Explicitly call out files in package.json #87
Closed
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.
Explicitly call out which files should be included in the published NPM package. This will keep tests, benchmarks, examples, and other non-essential files from making the package larger than it needs to be. The GitHub repository is correctly marked in the package file, so any user that wants these things
can have ready access to them online.
README.md and LICENSE are always included.
Fixes #78.
New output of
npm pack --dry-run
:I tested this to ensure I got all of the important files by:
Note that there is not a "benchmark" script in package.json, so I haven't run
npm run benchmark
as requested below.Checklist
npm run test
andnpm run benchmark
and the Code of conduct