No EXTRANEOUS package.
{
"name": "test",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "eslint ."
},
"dependencies": {
"@tanstack/react-query": "^5.90.12",
"@uidotdev/usehooks": "^2.4.1",
"axios": "^1.13.2",
"bootstrap": "^5.3.8",
"next": "^16.0.7",
"next-auth": "^5.0.0-beta.27",
"react": "^19.2.1",
"react-bootstrap": "^2.10.10",
"sharp": "^0.34.5",
"zod": "^4.1.13"
},
"devDependencies": {
"@types/node": "^24.10.1",
"baseline-browser-mapping": "^2.9.2",
"eslint": "^9.39.1",
"eslint-config-next": "^16.0.7",
"typescript": "^5.9.3"
}
}
$ rm -rf node_modules/ package-lock.json
$ npm i
...
$ npm ls --all --parseable --long --omit=dev --omit=optional | grep EXT
.../npm_test/node_modules/@emnapi/runtime:@emnapi/[email protected]:EXTRANEOUS
$ uname -ra
Linux <hostname> 6.1.0-41-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.158-1 (2025-11-09) x86_64 GNU/Linux
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
The
npm lscommand lists an EXTRANEOUS package, that doesn't appear to be removable.Not sure if it's an upstream package dependency problem, mind.
Expected Behavior
No EXTRANEOUS package.
Steps To Reproduce
With package.json:
Steps:
Environment