Turbopack Error: create symlink ... (Upgrade to Nextjs v16.1) ... Turbopack Error: create symlink to ../../node_modules/jsdom

[lluz]

Deleted folders 'node_modules' and '.next'
Upgraded these packages in my project (from v16.0.10):
"@next/third-parties": "16.1.0"
"next": "16.1.0"
"eslint-config-next": "16.1.0"

Result:
Can no longer build or compile the project with regular VSCode editor windows open in non-Admin mode.
Dev run presents the issue after it consoles the message 'Compiling /[[...urlParams]] ...', and after that it hangs on the message 'Compiling /_error ...'.

Poor mitigation:
Opening the editor in Admin mode, clears the issue ... but makes it harder to open more than 1 editor window :(

System Context:

• Microsoft Windows 11 Pro 10.0.26100 Build 26100
• VSCode 1.107.1 (user setup)
• Using package "isomorphic-dompurify": "2.34.0" (that depends on 'jsdom')
• Everything runs fine while using NextJS v16.0.10
• Never had a similar issue like this that required to open the editor in Admin mode to get Nextjs to build or compile.
• Reproduced this in a MacOS Vscode, and the issue does NOT occur.

ERROR presented (next build):

Turbopack version: ea1df5f2
Next.js 16.1.0 (Turbopack)

Error message:

create symlink to ../../node_modules/jsdom

Caused by:
- A required privilege is not held by the client. (os error 1314)

Additional terminal info on next build:

Next.js 16.1.0 (Turbopack)
- Environments: .env.local

  Creating an optimized production build ...

-----
FATAL: An unexpected Turbopack error occurred. A panic log has been written to C:\Users\[user]\AppData\Local\Temp\next-panic-xxxxxx.log.

To help make Turbopack better, report this error by clicking here.
-----

> Build error occurred
Error [TurbopackInternalError]: create symlink to ../../node_modules/jsdom

Caused by:
- A required privilege is not held by the client. (os error 1314)
    at ignore-listed frames {
  type: 'TurbopackInternalError',
  location: undefined
}

 *  The terminal process "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Command npm run build" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it. 

Seems like a lot of people, is the Discussions section, have the same issue...

[ct-dixit]

The same issue comes up with the @react-pdf/renderer package.

[FeelGoodInc]

Same issue for classnames package

[icyJoseph]

Try to enable Windows Developer Mode and see if that helps.

• https://blogs.windows.com/windowsdeveloper/2016/12/02/symlinks-windows-10
• https://learn.microsoft.com/en-us/windows/advanced-settings/developer-mode

[KryptoBeard]

Same issue, random packages... works with dev mode, which I've never enabled before.

[icyJoseph]

It's cuz symlinks on Windows... PR w/ fix has been merged: #87606

[bgw]

We believe this issue is fixed in Next 16.1.1. Please upgrade to that version, and file a new issue or discussion if you encounter any similar problems. Closing as duplicate of #86668.

[kachkaev]

It might have been fixed on Windows but not for AWS Amplify: aws-amplify/amplify-hosting#4074

[bgw]

Thanks for the heads-up. I left a comment there: aws-amplify/amplify-hosting#4074 (comment)