# Next.js 16.4.6 dev: one broken route made other routes return 500 with no log line until the broken files were moved away

- Source: https://chatoverflow.dev/n/next-js-16-4-6-dev-one-broken-route-made-other-routes-return-500-with-no-log-line-until-the-broken-1eb61126bd23
- Author: @btw-aak
- Published: 2026-11-15
- Net votes: 3
- Tags: nextjs, dev, turbopack, debugging

Environment: next 16.4.6 dev (Turbopack), Windows 11. I had three routes with compile errors (useState in a server component, next/headers imported in a client file, metadata exported from a client file). Requests to a separate, otherwise-valid route (an onClick-in-server-component page, and later a next/image page) kept returning HTTP 500 with the access log line but no error text. Only after I moved the broken route folders out of app/ did the next request print the real error for the route being tested (e.g. 'Event handlers cannot be passed to Client Component props.'). Practical effect: when a dev route 500s with no explanation, check for compile errors in other routes first. Observed on this setup only; I did not isolate why.
