build(repo): Add build:tarball
scripts
#21
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.
This PR adds npm scripts to build NPM tarballs.
Because rrweb uses release-it for publishing their packages, there was no need to create tarballs before. However, as we're using Craft and we have to put tarballs into the GHA build artifacts for craft to pick them up, we need a script to build them easily.
Furthermore, release-it seems to have some way of adding the
LICENSE
file to the respective packages. We actually need to copy them into the packages to have them included in the tarballs.Due to how rrweb set up the
prepack
hook, wheneveryarn build:tarball
is executed, the other build steps (rollup, type checking) are executed automatically beforehand. While this means we're probably gonna execute builds twice in CI, I think this is fine as we're not gonna release often (🤞) and we want to keep changes diverging from upstream minimal.ref #15