nextjs - 💡(How to fix) Fix Bug: Tailwind fails with ENOENT for existing file when using Turbopack [1 comments, 2 participants]

Link to the code that reproduces this issue

not available

To Reproduce

1. Create a Next.js project using Turbopack

2. Configure Tailwind CSS with a standard content glob:

   "./app/**/*.{js,ts,jsx,tsx}"

3. Add files under nested route groups and dynamic segments (e.g. [locale], (main))

4. Start the dev server with pnpm dev

5. Observe intermittent or persistent ENOENT errors for existing files

Current vs. Expected behavior

Expected behavior

Tailwind should correctly detect and scan existing files without throwing ENOENT errors.

Actual behavior

Tailwind attempts to stat an existing file and fails with ENOENT, breaking the build.

Possible cause

There may be a mismatch between Tailwind’s file tracking (resolveChangedFiles) and Turbopack’s virtual filesystem or watcher, especially with:

• dynamic route segments ([locale])
• route groups ((main))

Provide environment information

* Framework: Next.js 16.2.1 (Turbopack enabled)
* Styling: Tailwind CSS 3.4.19
* Package manager: pnpm
* OS: macOS

Which area(s) are affected? (Select all that apply)

CSS

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

• Clearing .next and caches DOES resolve the issue
• The problem appears related to file tracking or invalidation when using Turbopack
• The issue may be related to how Tailwind tracks changed files in combination with Turbopack’s filesystem layer