2 people reported
All time, since Aug 25.
Dev server 404s dynamic subroutes
“Some boots serve the class, some boots 404 all of it.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/next-js/issues/4218/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Dev server intermittently 404s routes below dynamic segments. Turbopack next dev reports Ready with a partial route graph; missing routes persist for the session, more often under CPU load.
Is this your bug?
File my report- Where
- Turbopack dev server
- Versions
- 16.3.1 to 16.3.5
- Platforms
- Linux, Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Navigation stalls with repeated 307s1 person
- Page module factory not available20 people
- Prefetch crashes shallow navigation1 person
Original reports4, newest first
- Turbopack dev server reports Ready with a partial route graph; missing routes never register (persists for the life of the process)On GitHub#98985
- Dev server (Turbopack): all child routes below a dynamic segment inside route groups intermittently 404 for an entire next dev session; any file event under app/ repairs the routerOn GitHub#97897
- Dev server (Turbopack): all child routes below a dynamic segment inside route groups intermittently 404 for an entire next dev session; any file event under app/ repairs the routerOn GitHub#97896
- Dev server (Turbopack): all child routes below a dynamic segment inside route groups intermittently 404 for an entire next dev session; any file event under app/ repairs the routerOn GitHub#97894