Question Details

No question body available.

Tags

reactjs node.js windows next.js

Answers (1)

Accepted Answer Available
Accepted Answer
December 10, 2025 Score: 6 Rep: 104 Quality: High Completeness: 70%

The issue was caused by Turbopack, which is the default bundler in Next.js 16. On Windows 11, I think Turbopack can fail during file system operations (especially renaming temporary manifest files), which makes bot next dev and next build exit without any errors. I think this is an issue related to Windows file locking.

I fixed the problem by switching back to Webpack, which avoids these issues entirely.

Updated scripts in package.json:

"scripts": { "dev": "next dev --webpack", "build": "next build --webpack", "start": "next start" }

After adding the --webpack flag, both development and production builds work normally again.