Package cleanup: reduce published files and dependencies (#126, #127) #128
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.
Addresses #126 and #127 in a single PR.
I don’t think there is a way to test the dependencies removal apart from
npm install
ing the published package. For the removal of unneeded files, here is the command I would recommend using, to inspect what would be part of the package’s tarball onnpm publish
:And here is the diff of that command’s output before and after the switch from
.npmignore
to the package.jsonfiles
:Note how even if the pattern is only
lib
, npm will always include the project’s package.sjon, README, license, and CHANGELOG.This change is