-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
peerDependencies
not resolving properly
#7932
Comments
Can you provide a more complete reproduction? |
This is the most recent repro i can remember. |
Possibly related #7869 |
I can attest to this being an issue while using Elysia. I have to delete Elysia from the Elysia plugin's node_modules and re-install it to fix it. |
* updating package with child peerDependency doesn't keep old version * [autofix.ci] apply automated fixes * fixed TODO test * [autofix.ci] apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
What version of Bun is running?
1.0.20+09d51486e
What platform is your computer?
Linux 5.15.133.1-microsoft-standard-WSL2 x86_64 x86_64
What steps can reproduce the bug?
Install a a package that requires a peerDependency to work, also install said peerDependency.
Afterwards, try to update the peerDependency.
If you are using typescript you will find lots of type collisions because of missmatched versions, if you observe further you will see that bun has installed 2 versions of the dependency instead of just having the one you updated
What is the expected behavior?
I expect bun to just have 1 version of the dependency
What do you see instead?
Bun installs multiple versions
Additional information
No response
The text was updated successfully, but these errors were encountered: