nextjs - 💡(How to fix) Fix Typed Route Validator Fails on .tsx Routes — Hardcoded .js Reference Persists After Deletion [1 comments, 2 participants]

1. Delete .next, disable typedRoutes, rename folders, create stubs — error persists
2. Confirm that the error does not appear locally after cleanup, but reappears during Vercel deployment, even with cache disabled
3. Validator continues to reference the deleted .js file, causing a TypeScript error: Current behavior- Build fails with a TypeScript error: I’ve already tried clearing .next, reinstalling node_modules, restarting the machine, and even renaming route folders — all from PowerShell as admin. The validator error persists regardless of environment or tooling. Despite all of this, the validator continues to auto-generate a reference to ../../app/home/page.js, even though the actual route is defined in page.tsx and no .js file exists. This causes a TypeScript error during build and blocks deployment. This issue affects emotionally sensitive legacy workflows where stability and clarity are essential. I’m reporting this without a reproduction repo because the bug is reproducible in any clean Next.js 15 setup using the App Router and .tsx routes. I’ve done everything possible to isolate and resolve it locally. I would highly appreciate your help with the reproduction repo, as I’m new to all of this and currently using Copilot to navigate the process. I find it quite long-winded to create a separate repo just for this validator error, especially since the issue is reproducible in a clean Next.js 15 setup. I can’t make my current project public, as it contains sensitive code that I don’t yet have protection for. Thank you in advance for your understanding and support. I’ve now confirmed that the error only appears during Vercel deployment. My local build is clean — no validator errors, no reference to page.js, and no duplicate route warnings. The validator error reappears on Vercel even with cache disabled and a clean Git history. This suggests that the validator is regenerating stale route references during deployment, despite the .js file being fully removed. I’ve validated this multiple times from PowerShell with a clean build and confirmed that the issue is isolated to Vercel’s build environment.

TL;DR

The most likely fix is to manually intervene in the auto-generated validator.ts file to correct the hardcoded import reference to use the .tsx file instead of the non-existent .js file.

Guidance

• Verify that the issue is indeed caused by the auto-generated validator.ts file referencing a deleted .js file by checking the file's contents and the error message.
• Try manually correcting the import statement in validator.ts to point to the correct .tsx file, and see if the error resolves.
• Investigate why the typedRoutes disablement is not preventing the validator generation as expected, and consider exploring alternative configurations or workarounds.
• Since the issue only appears during Vercel deployment, explore Vercel-specific settings or environment variables that might be influencing the behavior.

Notes

The provided information suggests that the issue is related to the auto-generated validator.ts file and its hardcoded import reference. However, without a reproduction repository, it's challenging to provide a definitive solution. The suggestions above are based on the information provided and may require further investigation and experimentation to resolve the issue.

Recommendation

Apply a workaround by manually correcting the validator.ts file or exploring alternative configurations to prevent the validator from generating a reference to the deleted .js file. This is recommended because the issue seems to be related to the auto-generated file and the typedRoutes configuration, and a workaround might be necessary until a more permanent solution is found.