[BUG] Workspace lifecycle scripts silently skipped under install-strategy=linked #9982

Activity

1. manzoorwanijk

   added

   Bugthing that needs fixingthing that needs fixing

   Needs Triageneeds review for next stepsneeds review for next steps

   on Sep 15, 2026
2. saitanallensantiago26-beep commented on Sep 15, 2026

   

   saitanallensantiago26-beep

   on Sep 15, 2026

   More actions

   Is there an existing issue for this?

   • I have searched the existing issues

   This issue exists in the latest npm version

   • I am using the latest npm

   This is not just a request to bump a dependency for a CVE

   • This is not solely a request to bump a dependency for a CVE

   Current Behavior

   With install-strategy=linked, npm install does not run a workspace's preinstall, install, postinstall or prepare scripts. Nothing is logged, the unreviewed scripts advisory does not list the workspace, and --strict-allow-scripts still exits 0. Hoisted on npm 12 and linked on npm 11.19.1 run all four.

   Expected Behavior

   Workspace scripts run under linked, as they do under hoisted, since workspaces are exempt from the allowScripts gate.

   Steps To Reproduce

   mkdir x && cd x
   mkdir -p packages/a
   echo '{"name":"r","version":"1.0.0","workspaces":["packages/*"]}' > package.json
   echo '{"name":"a","version":"1.0.0","scripts":{"postinstall":"touch post.txt","prepare":"touch prepared.txt"}}' > packages/a/package.json
   npm install --install-strategy=linked --no-audit --no-fund
   ls packages/a   # expected: package.json post.txt prepared.txt, actual: package.json

   Environment

   • npm: 12.0.2 and latest (c9876d7)
   • Node.js: v24.18.0
   • OS Name: macOS Darwin 25.6.0
3. saitanallensantiago26-beep commented on Sep 15, 2026

   

   saitanallensantiago26-beep

   on Sep 15, 2026

   More actions

   Is there an existing issue for this?

   • I have searched the existing issues

   This issue exists in the latest npm version

   • I am using the latest npm

   This is not just a request to bump a dependency for a CVE

   • This is not solely a request to bump a dependency for a CVE

   Current Behavior

   With install-strategy=linked, npm install does not run a workspace's preinstall, install, postinstall or prepare scripts. Nothing is logged, the unreviewed scripts advisory does not list the workspace, and --strict-allow-scripts still exits 0. Hoisted on npm 12 and linked on npm 11.19.1 run all four.

   Expected Behavior

   Workspace scripts run under linked, as they do under hoisted, since workspaces are exempt from the allowScripts gate.

   Steps To Reproduce

   mkdir x && cd x
   mkdir -p packages/a
   echo '{"name":"r","version":"1.0.0","workspaces":["packages/*"]}' > package.json
   echo '{"name":"a","version":"1.0.0","scripts":{"postinstall":"touch post.txt","prepare":"touch prepared.txt"}}' > packages/a/package.json
   npm install --install-strategy=linked --no-audit --no-fund
   ls packages/a   # expected: package.json post.txt prepared.txt, actual: package.json

   Environment

   • npm: 12.0.2 and latest (c9876d7)
   • Node.js: v24.18.0
   • OS Name: macOS Darwin 25.6.0
4. v-mragunandhan24

   removed

   Needs Triageneeds review for next stepsneeds review for next steps

   on Sep 29, 2026
5. nkolev92

   added

   Priority 3

   install-linked-strategy

   Priority 2secondary priority issuesecondary priority issue

   and removed

   Priority 3

   on Sep 29, 2026
6. manzoorwanijk

   added 18 commits that reference this issue on Oct 1, 2026

   Framework: Allow the @wordpress/icons prepare script

   ...

   122cee6

   Framework: Allow the @wordpress/icons prepare script

   ...

   08de4c8

   Framework: Update npm to v12

   ...

   5fdb2d7

   Framework: Update npm to v12

   ...

   486da49

   Framework: Update npm to v12

   ...

   c1d81ed

   Framework: Update npm to v12

   ...

   50f9da9

   Framework: Update npm to v12

   ...

   d1f8d8a

   Framework: Update npm to v12

   ...

   2d23770

   Framework: Update npm to v12

   ...

   de6139f

   Framework: Update npm to v12

   ...

   25af696

   Framework: Update npm to v12

   ...

   bfd0a36

   Framework: Update npm to v12

   ...

   af1a067

   Framework: Update npm to v12

   ...

   c131acd

   Framework: Update npm to v12

   ...

   f8b05e7

   Framework: Update npm to v12

   ...

   b7c251f

   Framework: Update npm to v12

   ...

   864089d

   Framework: Update npm to v12

   ...

   b5e438a

   Framework: Update npm to v12

   ...

   927a931
7. manzoorwanijk

   added 2 commits that reference this issue on Oct 14, 2026

   Framework: Update npm to v12

   ...

   0caf5fc

   Framework: Update npm to v12

   ...

   4778afc