-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Dedupe packages #61532
Dedupe packages #61532
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: -10 B (0%) Total Size: 1.74 MB
ℹ️ View Unchanged
|
3c88ba3
to
bd4013c
Compare
It would be nice to make it harder to get into this state. Generally we don't want package duplication if we can avoid it. |
I think there's a few options. If we want this to happen automatically, it seems we can add If we want it to be more intentional, we could create an audit workflow that runs I think I prefer the first option, but there may be some consequences of changing the strategy that are not immediately apparent. |
Nice @desrosj! I think |
What?
Dedupe JavaScript dependencies.
Why?
Reducing dependency duplication is beneficial in general:
This will likely make it easier to upgrade certain packages in the future.
This will be helpful for #61486
How?
Run
npm dedupe
until it no longer changes the package-lock.json file.Fix resulting test errors.
Testing Instructions
Automated testing should be sufficient here.