-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pnpm install behavior inconsistent with flags #1878
Milestone
Comments
zkochan
added a commit
that referenced
this issue
Jun 20, 2019
zkochan
added a commit
that referenced
this issue
Jun 20, 2019
zkochan
added a commit
that referenced
this issue
Jun 20, 2019
🚢 3.5.2 |
Thanks Zoltan. Verified that this no longer repros on my repro repo with pnpm 3.5.2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pnpm version: 3.5.1
Lockfile version: 5.1
Repro repo:
https://github.com/sachinjoseph/pnpm-install-lockfile-bug
Expected behavior:
pnpm install should not update the lockfile if the current lockfile satisfies the package.jsons (unless or the lockfile version needs an upgrade
If pnpm install
--frozen-lockfile
can succeed, then pnpm install shouldn't update the lockfile (unless the lockfile version needs an upgrade).If
pnpm install
can succeed without updating the lockfile, then pnpm install--lockfile-only
should not update the lockfile.Actual behavior:
Not only does pnpm install update the lockfile when it is not necessary, but also the behavior is inconsistent with different flags.
react-focus-lock
version is1.17.7
inpnpm-lock.yaml
before running these commands.In folder
package1
$ cd (repo-root/package1
--frozen-lockfile
--lockfile-only
react-focus-lock
version inpnpm-lock.yaml
In folder
package2
$ cd (repo-root/package2
--frozen-lockfile
--lockfile-only
Additional information:
react-focus-lock
's version (and its integrity hash).node -v
prints: v10.15.3The text was updated successfully, but these errors were encountered: