Skip to content
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

resolution-mode lowest-direct and time-based doesnot works as expected #7750

Open
1 of 4 tasks
andriyor opened this issue Mar 9, 2024 · 1 comment · May be fixed by #7824
Open
1 of 4 tasks

resolution-mode lowest-direct and time-based doesnot works as expected #7750

andriyor opened this issue Mar 9, 2024 · 1 comment · May be fixed by #7824

Comments

@andriyor
Copy link

andriyor commented Mar 9, 2024

Verify latest release

  • I verified that the issue exists in the latest pnpm release

pnpm version

8.15.4

Which area(s) of pnpm are affected? (leave empty if unsure)

Dependencies resolver

Link to the code that reproduces this issue or a replay of the bug

https://github.com/andriyor/pnpm-resolution-mode-bug

Reproduction steps

  1. config: resolution-mode=lowest-direct
  2. install some package with dependencies
  3. install package which is listed in dependencies of previous package but use lover version

Describe the Bug

  1. config: resolution-mode=lowest-direct
  2. i installed "msw": "1.2.2", which has node-fetch as dependencies and it revolved to 2.7.0 version
  3. install "node-fetch": "^2.6.1" and it also resolved to 2.7.0 version

Expected Behavior

but i expect to see node-fetch 2.6.1 version

Which Node.js version are you using?

18.16

Which operating systems have you used?

  • macOS
  • Windows
  • Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

No response

@andriyor
Copy link
Author

andriyor commented Mar 9, 2024

clean install without node_modules and lock file resolves to correct 2.6.1 version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant