feat(rush): update npm release process #2034
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.
Update our package format for releases. Instead of having our own custom release flow where packages are double-released based on their format we move to a
main/module/browser
output format. This cuts down on a lot of custom code and will allow us to release more easily / with more features like git tags which are currently looked over.Going to need to do some testing,
client-switch
in particular is a bit weird since it previously had 2 packages (default/esm-esnext) with 2 entrypoints for main/browser. Now it is just 1 package with 3 entrypoints for main/browser/module.