Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/github/vercel/next.js/tree/canary/examples/reproduction-template?file=%2F.gitignore

To Reproduce

npx create-next-app@latest next-test
cd next-test
npm ls

next-test
├── @emnapi/runtime@1.5.0 extraneous
├── @tailwindcss/postcss@4.1.14
├── @types/node@20.19.19
├── @types/react-dom@19.2.0
├── @types/react@19.2.0
├── next@15.5.4
├── react-dom@19.1.0
├── react@19.1.0
├── tailwindcss@4.1.14
└── typescript@5.9.3

@emnapi/runtime@1.5.0 extraneous cannot be removed.

Current vs. Expected behavior

Current:
emnapi/runtime@1.5.0 shows up as an extraneous dependency immediately after installation.

Running npm uninstall emnapi/runtime@1.5.0 or other cleanup commands (npm prune, reinstalling, clearing caches) does not remove it.

The dependency remains in node_modules marked as extraneous, causing confusion and potential build/runtime issues.

This extraneous dependency cannot be removed without abandoning Next.js altogether.

Expected:
I expected a clean install with no extraneous dependencies listed post install

Provide environment information

---**Environment:*** OS: Debian (latest stable)* Node.js: v22.x (LTS)* npm: v10+* Next.js: 15.5.4 (latest stable)

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

create-next-app

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

next build (local)

Additional context

No response