Documentation: Update details related to npm publishing #42364
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What and why?
I arrived at the Managing Packages page in Block Editor Handbook and I realized that we could include a few updates to the documentation based on the blog post WordPress packages publish to npm every two weeks that I published today.
I also realized that we keep outdated details for npm publishing in the README from
/packages
folder explaining how to maintain packages.How?
All the details for npm publishing are now covered in Packages Releases to npm and WordPress Core Updates so the best way moving forward is to reference that section from other places.