Stop publishing non-essential files (like tests and gruntfile) to npm #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.
I noticed that we were publishing a bunch of unnecessary files (like the
test
directory andgruntfile.js
) to npm. At best, this wastes space. At worst, we could accidentally publish some sensitive file (though that's unlikely).Tested this by:
npm pack
and verified that no unnecessary files were includedairtable-0.7.0.tgz
, into a temporary directorynpm i airtable-0.7.0.tgz
node -p "require('airtable')"
didn't breakSee documentation for the
files
key inpackage.json
for more info here.