nextjs - 💡(How to fix) Fix Tailwind config cannot import local TS modules in Next.js 16.1.x [3 comments, 4 participants]

• Error is reported as Module not found Not error

TL;DR

The issue can be fixed by adjusting the import paths or configuration in tailwind.config.ts to accommodate changes in Next.js 16.1.x.

Guidance

• Verify that the file paths in tailwind.config.ts are correct and try using absolute paths or paths relative to the project root.
• Check the Next.js documentation for any changes to how local modules are resolved in version 16.1.x.
• Consider downgrading to Next.js 16.0.10 temporarily to confirm if the issue is indeed related to the upgrade.
• Review the Turbopack configuration to ensure it is compatible with the new version of Next.js.

Example

No specific code example can be provided without modifying the original code, but adjusting import paths in tailwind.config.ts might look like changing import './local-module' to import '../../local-module' if the file structure has changed or if the resolution of modules has been altered by the Next.js update.

Notes

The exact solution may depend on the specifics of the project structure and how Next.js 16.1.x handles module imports differently than version 16.0.10. The provided environment information and the fact that the issue arises after a version upgrade suggest that the problem is related to compatibility changes.

Recommendation

Apply a workaround by adjusting import paths or configurations in tailwind.config.ts until a more permanent solution or an official fix from Next.js is available, as downgrading might not be a viable long-term solution.