Windows (`next-swc.node`): Use MSVC's `link.exe` rather than clang's `lld.exe` generating `next-swc.node` to avoid dynamic link issue.

[emmettlu]

Solution: Use MSVC's link.exe to generate next-swc.node binary. Never use clang's toolchain on Windows.

https://github.com/aaravlu/play_nextjs

I find out you just use clang's lld.exe to generate the final next-swc.node binary:

Note the linker version -- 14.0, the binary was linked by clang's lld.exe rather than MSVC's link.exe

~\Repos\play_nextjs> pnpm dev

> play_nextjs@0.1.0 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\@next+swc-win32-x64-msvc@16.0.1\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\@next+swc-win32-x64-msvc@16.0.1\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

Provide environment information

Solution: Use MSVC's `link.exe` rather than clang's `lld.exe` generating `next-swc.node` to avoid dynamic link issue.

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

SWC

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

next dev (local)

[emmettlu]

This repo's binary should be linked with MSVC's link.exe: https://www.npmjs.com/package/@next/swc-win32-x64-msvc

Then, this discussion could be answered.

[emmettlu]

Seems no this issue.

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.