nextjs - 💡(How to fix) Fix Windows (`next-swc.node`): Use MSVC's `link.exe` rather than clang's `lld.exe` generating `next-swc.node` to avoid dynamic link issue. [3 comments, 2 participants]

~\Repos\play_nextjs> pnpm dev

[email protected] dev C:\Users\Administrator\Repos\play_nextjs next dev

⚠ Attempted to load @next/swc-win32-x64-msvc, but an error occurred: A dynamic link library (DLL) initialization routine failed . \?\C:\Users\Administrator\Repos\play_nextjs\node_modules.pnpm@[email protected]\node_modules@next\swc-win32-x64 -msvc\next-swc.win32-x64-msvc.node ▲ Next.js 16.0.1 (Turbopack)

• Local: http://localhost:3000
• Network: http://192.168.122.242:3000

✓ Starting... Skipping creating a lockfile at C:\Users\Administrator\Repos\play_nextjs.next\dev\lock because we're using WASM bindings Error: turbo.createProject is not supported by the wasm bindings. at ignore-listed frames ⚠ Attempted to load @next/swc-win32-x64-msvc, but an error occurred: A dynamic link library (DLL) initialization routine failed . \?\C:\Users\Administrator\Repos\play_nextjs\node_modules.pnpm@[email protected]\node_modules@next\swc-win32-x64 -msvc\next-swc.win32-x64-msvc.node

 ELIFECYCLE  Command failed with exit code 3221225477. ~\Repos\play_nextjs> node -p "process.arch" x64

TL;DR

Use MSVC's link.exe to generate the next-swc.node binary instead of clang's lld.exe to resolve the dynamic link library initialization routine failure.

Guidance

• Verify that the next-swc.node binary is being generated using MSVC's link.exe by checking the linker version.
• Ensure that the @next/swc-win32-x64-msvc package is installed and configured correctly.
• Try reinstalling the @next/swc-win32-x64-msvc package using pnpm to ensure that the correct binary is generated.
• Check the environment variables and configuration files to ensure that MSVC's link.exe is being used instead of clang's lld.exe.

Example

No code snippet is provided as the issue is related to the build process and linker configuration.

Notes

The issue seems to be specific to the Windows environment and the use of clang's lld.exe instead of MSVC's link.exe. The solution provided in the issue body suggests using MSVC's link.exe to generate the next-swc.node binary.

Recommendation

Apply workaround: Use MSVC's link.exe to generate the next-swc.node binary, as suggested in the issue body, to avoid the dynamic link library initialization routine failure. This is because the issue is caused by the use of clang's lld.exe instead of MSVC's link.exe, and switching to MSVC's link.exe should resolve the issue.