-
-
Notifications
You must be signed in to change notification settings - Fork 941
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
doesn't resolve to latest satisfied version #7543
Comments
So why don't you run |
In my opinion, when I remove lockfile, the install result should be the same whether or not the node_modules exits. node_modules shouldn't affect the install result.
|
I am not sure what made you believe that. Historically, npm didn't even have a lockfile by default and running That said, I don't know what most people would expect. However, I think this is the first time I hear about this expectation. |
I'm wrting a article about |
Verify latest release
pnpm version
8.14.1
Which area(s) of pnpm are affected? (leave empty if unsure)
No response
Link to the code that reproduces this issue or a replay of the bug
https://stackblitz.com/~/github.com/tjx666/mono-project
Reproduction steps
pnpm install
, packages/pkg1 will install @yutengjing/foo v1.0.0 because of the lockfilerm pnpm-lockfile.yaml
pnpm install
, packages/pkg1 should install @yutengjing/foo v1.0.2 but still install v1.0.0Describe the Bug
When I remove lockfile, and reinstall, packages/pkg1 still install v1.0.0
Seems affected by the node_modules. If I remove the node_modules, everythings ok.
Expected Behavior
should install @yutengjing/foo v1.0.2. Because I decalre the version by
^1.0.0
, and the latest version is v1.0.2.Which Node.js version are you using?
18.8
Which operating systems have you used?
If your OS is a Linux based, which one it is? (Include the version if relevant)
No response
The text was updated successfully, but these errors were encountered: