-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Docs: Clarify how to update a dependency for existing packages #16923
Conversation
My biggest problem was that I assumed |
Yes, the issue is that for some reasons |
Doesn't |
Did you try or do you guess? |
Both! Recall that's what I did first before talking to you originally about this. |
Can you advice how the process should look like with |
I believe it would prevent having to remove and re-add packages when attempting to update a nested dependency. You should in theory just have to update the package.json and bootstrap. There's not a ton different I suppose than to what you're describing so it might just be easier for everyone to stick with what you wrote since everybody knows the |
It seems to be a bit easier when I read it :) I merged this PR to have any hints present but I will give it a go and see if I can further refine docs. Thanks! |
Description
This is a follow-up for #16876 where I added some hints on how to add a new dependency to one of the WordPress packages. This time I add more details for removing and updating dependencies.
It was triggered by the discussion in #16875. I tested it myself when upgrading ESLint and its plugins to the latest version in #16921.
Preview new version of docs here:
https://github.com/WordPress/gutenberg/blob/db23b8c4abeb6c8711060e78cfbab1648ad7f27a/packages/README.md#managing-dependencies