Explicitly define contents of npm package #161
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
|
is this new? |
|
No, it's been in npm for at least a couple of years: isaacs/npm@144b26a#L9R0 I recently discovered it and now much prefer to explicitly define what goes into my packages than having a long list of ignores in a separate file. Hopefully you'll agree. |
|
I'm going to have to start doing this now. Thanks @sindresorhus. |
|
weird! |
tj
added a commit
that referenced
this pull request
Jul 30, 2013
Explicitly define contents of npm package
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.
No description provided.