diff options
author | Stuart P. Bentley <stuart@testtrack4.com> | 2014-09-30 22:17:25 -0700 |
---|---|---|
committer | Stuart P. Bentley <stuart@testtrack4.com> | 2014-09-30 22:17:25 -0700 |
commit | 2d111edfb0475c08d325a3cbebee0a9b8e54c351 (patch) | |
tree | f79e1a66a89ccae12d3afdd522dc65682ce1812f /Node.gitignore | |
parent | 298588469ac0cb08a00eebf7b00efb5ab726daca (diff) | |
download | gitignore-2d111edfb0475c08d325a3cbebee0a9b8e54c351.tar.gz gitignore-2d111edfb0475c08d325a3cbebee0a9b8e54c351.zip |
Restore original comment about node_modules
It's not the opinion of "some people", it's a conditional circumstance.
Even proponents of checking node_modules into Git agree that you
shouldn't do it when you're writing a module to be included as a
dependency on npmjs.org: the advantage of checking node_modules
into Git is only for fully-packaged apps, which is why the original
comment was what it was.
Diffstat (limited to 'Node.gitignore')
-rw-r--r-- | Node.gitignore | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Node.gitignore b/Node.gitignore index 59d842ba..bf988676 100644 --- a/Node.gitignore +++ b/Node.gitignore @@ -20,7 +20,7 @@ coverage build/Release # Dependency directory -# Commenting this out is preferred by some people, see +# Deployed apps should consider commenting this line out: # https://www.npmjs.org/doc/misc/npm-faq.html#should-i-check-my-node_modules-folder-into-git- node_modules |