You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Error in production but not caught by linter via pnpm build #167
I discovered a bug because I was trying to figure out why my code was building and deplying without errors then upon visiting the deployed website getting the response back from the url in return.
Google Chrome | 140.0.7339.128 (Official Build) (64-bit) (cohort: Stable)
Revision | 36aa3351631d175ee5346a1aaf74ef5d49abe308-refs/branch-heads/7339@{#1850}
OS | Windows 11 Version 24H2 (Build 26100.6584)
I tried to reproduce this on the latest generator/build pipeline by creating a fresh app, exporting a value from a route, importing it into a component, then running full production build + server start. I could not reproduce a runtime 500 locally.\n\nGiven this is likely deployment-adapter/runtime specific (e.g. Vercel preset/runtime behavior) rather than scaffold generation, can you provide an updated minimal repro against latest plus exact deploy target/config (adapter, Node runtime, env, and logs)? If reproducible on latest, we should likely track it in the Start runtime repo with that repro.
Activity
tannerlinsley commentedon Feb 17, 2026
I tried to reproduce this on the latest generator/build pipeline by creating a fresh app, exporting a value from a route, importing it into a component, then running full production build + server start. I could not reproduce a runtime 500 locally.\n\nGiven this is likely deployment-adapter/runtime specific (e.g. Vercel preset/runtime behavior) rather than scaffold generation, can you provide an updated minimal repro against latest plus exact deploy target/config (adapter, Node runtime, env, and logs)? If reproducible on latest, we should likely track it in the Start runtime repo with that repro.
eric-sison commentedon Jun 4, 2026
I'm seeing the same issue with nitro on a freshly generated project.
Project scaffold:
Running it in dev is fine, but
pnpm build && pnpm previewcauses this issue