feat(publish): add publishing options #5
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.
Splits the publishing config in different files.
To test before merging:
To add before mering:
yarn install --development
ornpm ci
to the NPM publishFor the last step; I intentionally did not do this as this once again would have led to a difference between
yarn
andnpm
. However, I feel like this should be a step part of the "built-and-lint" flow instead, where you write atest
that checks if all your packages can be installed without issues. How this would look like under the hood I am unsure, but that is a problem for later.