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
We currently use pnpm for our monorepo project, and we've had a few issues with the pnpm-lock.yaml file being broken.
Usually, our CI will notify us that the lock-file has to be updated if it goes stale when pnpm install runs. Since pnpm install fails when the lock-file is stale, the CI failed, too.
However, if a PR's lock-file is broken, pnpm install will issue a warning, making our CI checks pass with no issue which is not what we want.
This is why we are wondering whether pnpm install should also fail when the lock file is broken, that is, is it a planned feature? Or should we check for the state of the lock file through other means (pnpm list for example)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
We currently use
pnpm
for ourmonorepo
project, and we've had a few issues with thepnpm-lock.yaml
file being broken.Usually, our CI will notify us that the lock-file has to be updated if it goes stale when
pnpm install
runs. Sincepnpm install
fails when the lock-file is stale, the CI failed, too.However, if a PR's lock-file is broken,
pnpm install
will issue a warning, making our CI checks pass with no issue which is not what we want.This is why we are wondering whether
pnpm install
should also fail when the lock file is broken, that is, is it a planned feature? Or should we check for the state of the lock file through other means (pnpm list
for example)?Beta Was this translation helpful? Give feedback.
All reactions