Updated:

Next.js

Known bugs and feature requests, from its public GitHub issues and its public forum.

Vercel sheets: Platform Next.js

Oct 25Nov 7, 2026Oct 25 to Nov 7, 2026: 83 reports

Whole days, US Eastern time.

Bugs80 in the rangeTop 5

  1. 4 JS chunks downloaded twice“A CORS request and a no-CORS request for the same URL have different HTTP cache keys, so the second tag downloads the chunk again.” No workaround yet
  2. 4 Stale cache mix after redeploy“This is a problem when deploying new app versions while clients have cached resources from older builds.” No workaround yet
  3. 2 Hash links concatenate fragments“Every subsequent hash navigation on that route keeps prepending: /#a#c, /#a#b#d after another reload, etc.” No workaround yet
  4. 2 /_global-error prerender crash“On the reporter's machine this standalone scaffold builds green (~11 consecutive builds), while the production app crashes nondeterministically (~95% of runs).” No workaround yet
  5. 2 Back button skips history entries“Current: Back lands on /items/a, and /items is skipped.” Has a workaround
  6. 2 Validator.ts unused imports error“.next/dev/types/validator.ts(5,50): error TS6196: 'AppRouteHandlerRoutes' is declared but never used.” No workaround yet
  7. 2 Page reload loop after restart“Current (16.4.1): sessions 2 and 3 reload /a about 240 times in 6 seconds.” Has a workaround
  8. 1 remotePatterns wildcard matches too much“When the * is not the leftmost label, this lets hosts owned by anyone through the allowlist.” No workaround yet
  9. 1 Revalidation takes effect late“The revalidated page is still served from the cache until the gap between the two clocks has elapsed.” No workaround yet
  10. 1 Render loop from default parameterIn the minified build the module-level function is inlined into the default parameter, so the effect dependency changes each render and the render count never settles. Has a workaround
  11. 1 Route Handlers drop Content-Length“Viewers that rely on progressive/range loading now download the whole PDF before rendering the first page.” No workaround yet
  12. 1 Navigation stalls with repeated 307s“Click does nothing for ~8-10s, then the page updates via full-document fallback.” No workaround yet
  13. 1 Intercepted route ignores params“The URL becomes /items?tab=archive, and the link now reads Open dialog (/items/dialog?tab=archive).” No workaround yet
  14. 1 Framework 4xx responses become 500 in App Router-only production“Both requests return 500 Internal Server Error with a plain text body, and nothing is logged.” No workaround yet
  15. 1 Slow Turbopack production build“On a mid-sized app, next build (Turbopack) is about 30× slower on 16.4.x than on 16.3.8, and the problem is already fixed on the 16.5 canary line.” No workaround yet
  16. 1 Missing aarch64 SWC artifact“Same missing swc artifact as the build integration job.” No workaround yet
  17. 1 Namespace re-exports not tree-shaken“Turbopack ships lib/locales in the client bundle.” No workaround yet
  18. 1 Glob import returns undefined“next build renders {}, because every value is undefined.” No workaround yet
  19. 1 cookies() throws InvariantError in dev when form submits before hydration“Open / in a browser with JavaScript disabled (or submit the form before hydration finishes).” No workaround yet
  20. 1 Config imports resolve against cwd“When the working directory is not the project directory, relative imports in next.config.ts are resolved against process.cwd().” Has a workaround
  21. 1 Navigation waits on prefetchClicking a Link while the target's segment-data prefetch is still in flight delays the URL change and loading.js, unlike 16.3.8. No workaround yet
  22. 1 notFound() serves empty HTML“Current: a notFound() 404 serves <html id="__next_error__"><head></head><body></body></html>.” No workaround yet
  23. 1 Inline bootstrap blocked by CSP“Every other script in the same response (the per-request part) carries the nonce correctly.” Has a workaround
  24. 1 Build hangs on worker import cycle“Current: next build with Turbopack hangs silently.” Has a workaround

Feature requests2 in the rangeAll 0

Reports 83

grouped into

Bugs 80

Requests 2

Key

  • Rank in this list, by people
  • Has a workaround
  • Reports a week, thumbs-up outlined, this week white

Do you work on Next.js?

Claim its RAP Sheet to see what your users report and answer them in one place.