monorepo root .bin executable not working from workspace package directory · Issue #4858 · pnpm/pnpm · GitHub
More Web Proxy on the site http://driver.im/
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
monorepo root .bin executable not working when run from workspace package directory if ignore-scripts=true is set in .npmrc. One of my requirement for pnpm migration is to not run scripts due to supply chain attacks.
lets say there is a executable in root node_modules/.bin called app node_modules/.bin/app
pnpm app works from root directory. If I go to shared/client and run pnpm app it doesn't work - I get error ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL not found: app
Expected behavior:
monorepo root executables should work from anywhere when ignore-scripts=true is set.
Actual behavior:
monorepo root executables do NOT work except from root directory when ignore-scripts=true is set
Additional information:
node -v
v16.15.1
macOS
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
monorepo root .bin executable not working when run from workspace package directory if
ignore-scripts=true
is set in .npmrc. One of my requirement for pnpm migration is to not run scripts due to supply chain attacks.Works as expected if I remove
ignore-scripts=true
pnpm version:
7.1.7
Code to reproduce the issue:
Sample monorepo:
lets say there is a executable in root
node_modules/.bin
calledapp
node_modules/.bin/app
pnpm app
works from root directory. If I go to shared/client and runpnpm app
it doesn't work - I get errorERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL not found: app
Expected behavior:
monorepo root executables should work from anywhere when
ignore-scripts=true
is set.Actual behavior:
monorepo root executables do NOT work except from root directory when
ignore-scripts=true
is setAdditional information:
node -v
v16.15.1
macOS
The text was updated successfully, but these errors were encountered: