Prune NPM metadata fields from packages before re-publishing #14617
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.
The latest React release has some weird fields in the package JSON that weren't there in the canary. These fields (all beginning with "_") contain package registry meta data.
It's not ideal that we publish package with these fields still around. Technically, they aren't even valid since NPM rules and the packages JSON spec say that field names beginning with underscores are reserved.
So this PR adds a step that prunes these fields as part of preparing a stable release.
JSON diff before
JSON diff after