nextjs - 💡(How to fix) Fix next-env.d.ts toggles between .next/dev/types/routes.d.ts and .next/types/routes.d.ts even with typedRoutes: false [7 comments, 4 participants]

TL;DR

• The issue can be mitigated by ensuring that the next-env.d.ts file is not modified unnecessarily during dev and build runs, potentially by adjusting the script that adds imports to this file.

Guidance

• Review the dev and build scripts to understand why import "./.next/dev/types/routes.d.ts"; and import "./.next/types/routes.d.ts"; are being added to next-env.d.ts even when typedRoutes is disabled.
• Consider adding a conditional statement to these scripts to only add the import lines when typedRoutes is enabled.
• Investigate if there's a configuration option in Next.js or TypeScript that can prevent unnecessary modifications to the next-env.d.ts file.
• Verify that the typedRoutes option is correctly set to false in the Next.js configuration when running the dev and build scripts.

Example

No specific code example can be provided without knowing the exact scripts or configurations used, but the adjustment might look something like this:

if (typedRoutes) {
  // Add import lines to next-env.d.ts
}

Notes

• The exact solution depends on the specifics of the scripts and configurations used, which are not fully detailed in the issue.
• It's also possible that this behavior is a result of a version-specific issue with Next.js or TypeScript, but without more information, it's difficult to say for certain.

Recommendation

• Apply workaround: Adjust the scripts to conditionally add import lines based on the typedRoutes option to prevent unnecessary modifications to next-env.d.ts. This approach is recommended because it directly addresses the observed behavior without requiring upgrades or changes to dependencies that might introduce other issues.