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.

Sign up for GitHub

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

Jump to bottom

Leverage the "pnpm.overrides" field in the "pnpm link <destination>" command #3054

Closed
zkochan opened this issue Jan 2, 2021 · 1 comment
Closed

Leverage the "pnpm.overrides" field in the "pnpm link <destination>" command #3054

zkochan opened this issue Jan 2, 2021 · 1 comment
Labels
type: breaking change
Milestone
v10.0

Comments

@zkochan
Copy link
Member

zkochan commented Jan 2, 2021

Related issue: #3049

Our current implementation of pnpm link <destination> only links direct dependencies. Now that we have the pnpm.overrides field (which has the same and more features than yarn resolutions), we can make the link command automatically write the overrides for dependencies: direct and indirect.

This is similar to how Yarn's link command works: https://yarnpkg.com/cli/link
@zkochan zkochan added this to the v6.0 milestone Jan 2, 2021
@zkochan zkochan mentioned this issue Jan 2, 2021
Open
@zkochan zkochan modified the milestones: v6.0, v6.x Apr 3, 2021
@zkochan zkochan modified the milestones: v6.x, v8.0 Mar 8, 2023
@zkochan zkochan removed this from the v8.0 milestone Mar 29, 2023
@zkochan zkochan added this to the v10.0 milestone Nov 27, 2024
@zkochan
Copy link
Member Author

zkochan commented Nov 27, 2024

done in v10

@zkochan zkochan closed this as completed Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: breaking change
Projects
None yet
Milestone
v10.0
Development

No branches or pull requests
1 participant
@zkochan