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
pnpm i does not run ./my-command. But if shared-workspace-lockfile is enabled, it does. I would have expected it to work in both cases, and there doesn't seem to be anything in the docs to suggest otherwise.
Additional information:
node -v prints: v16.14.0
Windows, macOS, or Linux?: Linux
The text was updated successfully, but these errors were encountered:
When `shared-workspace-lockfile` is false,
opts.ignoreScripts is set to true since packages
are rebuild after recursive install.
However, it will cause `pnpm:devPreinstall` to be
skipped as well since it's not part of the rebuild
process.
This fix fixes the issue by checking whether the
--ignore-scripts flag is set from the source
instead
fixpnpm#4503
pnpm version:
6.32.3
Code to reproduce the issue:
.npmrc
:package.json
:pnpm-workspace.yaml
:Expected behavior:
pnpm i
runs./my-command
Actual behavior:
pnpm i
does not run./my-command
. But ifshared-workspace-lockfile
is enabled, it does. I would have expected it to work in both cases, and there doesn't seem to be anything in the docs to suggest otherwise.Additional information:
node -v
prints:v16.14.0
The text was updated successfully, but these errors were encountered: