You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[install-clients] Installing dependencies for clients/web...
npm error code EALLOWSCRIPTS
npm error --allow-scripts is not allowed in project-scoped installs. Add the entries to the "allowScripts" field in package.json, or to .npmrc, instead.
npm error A complete log of this run can be found in: /Users/jlh/.npm/_logs/2026-09-28T01_26_10_941Z-debug-0.log
[install-clients] npm install failed in clients/web (exit 1).
npm error code 1
npm error path /Users/jlh/_usr/src/gitClones/llm-mcpItems/inspector
npm error command failed
npm error command sh -c node scripts/install-clients.mjs
npm error A complete log of this run can be found in: /Users/jlh/.npm/_logs/2026-09-28T01_26_10_245Z-debug-0.log
~/_usr/src/gitClones/llm-mcpItems/inspector > less /Users/jlh/.npm/_logs/2026-09-28T01_26_10_245Z-debug-0.log
~/usr/src/gitClones/llm-mcpItems/inspector > node --version
v24.14.1
~/usr/src/gitClones/llm-mcpItems/inspector >
Severity 3 — npm install from a clone fails in the install-clients cascade with EALLOWSCRIPTS (npm config passed through to the per-client installs); npx users are unaffected
Urgency 2 — blocks building from source for affected npm configurations only
Bonuses: +1 bug label
Board: #28, Status Incoming (awaiting maintainer review — no milestone yet).
Fixed by #2713 (merged to v2/main); it ships in the next v2 release.
Cause:allow-scripts set in an npmrc (e.g. ~/.npmrc). npm exports every non-default config value to lifecycle scripts as npm_config_*. So our install-clients postinstall handed it to the per-client npm install, and npm 11.19+ rejects it there, because it arrives through the environment rather than an npmrc. Nothing about macOS was involved.
Workaround until the release: comment out the allow-scripts line in your npmrc while running npm install, or pull v2/main.
Activity
cliffhall commentedon Oct 12, 2026
Triage: Priority Medium (total 6)
npm installfrom a clone fails in theinstall-clientscascade withEALLOWSCRIPTS(npm config passed through to the per-client installs);npxusers are unaffectedbuglabelBoard: #28, Status
Incoming(awaiting maintainer review — no milestone yet).test(install): pin the symlinked-checkout guard and spawn node withou…
test(install): pin the env wiring with a stub npm, independent of the…
fix(install): canonicalize both sides of the main guard (#2518)
cliffhall commentedon Oct 13, 2026
Fixed by #2713 (merged to
v2/main); it ships in the next v2 release.Cause:
allow-scriptsset in an npmrc (e.g.~/.npmrc). npm exports every non-default config value to lifecycle scripts asnpm_config_*. So ourinstall-clientspostinstall handed it to the per-clientnpm install, and npm 11.19+ rejects it there, because it arrives through the environment rather than an npmrc. Nothing about macOS was involved.Workaround until the release: comment out the
allow-scriptsline in your npmrc while runningnpm install, or pullv2/main.fix(install): strip npm_config_allow_scripts from the per-client inst…