feat: publish package on NPM #172
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add two new CI tasks: one to build the standalone variant on push, and another one to publish an NPM package on release. The latter requires setting up a `NPM_TOKEN` secret in the GitHub repository settings. All dependencies are removed before publication because the published package is completely standalone: all of the dependencies are bundled in `dist/`. Add the "repository" field in package.json: it's a requirement for the npm publish --provenance flag.
This was referenced Aug 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This is the last part of #158.
Add two new CI tasks: one to build the standalone variant on push, and another one to publish an NPM package on release.
The latter requires setting up a
NPM_TOKENsecret in the GitHub repository settings.All dependencies are removed before publication because the published package is completely standalone: all of the dependencies are bundled in
dist/.Add the "repository" field in package.json: it's a requirement for the
npm publish --provenanceflag.Checklist
documentation/