Skip to content
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

feat(rush): update npm release process #2034

Merged
merged 1 commit into from May 20, 2020

Conversation

danwbyrne
Copy link
Contributor

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.

@danwbyrne danwbyrne force-pushed the rush-export branch 5 times, most recently from a1e331c to 3b25bfe Compare May 19, 2020 19:22
@danwbyrne danwbyrne force-pushed the rush-export branch 2 times, most recently from e53b27c to 27dd584 Compare May 19, 2020 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants