mirror of
https://github.com/github/gitignore
synced 2024-06-19 19:02:50 +02:00
2d111edfb0
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.
29 lines
590 B
Plaintext
29 lines
590 B
Plaintext
# Logs
|
|
logs
|
|
*.log
|
|
|
|
# Runtime data
|
|
pids
|
|
*.pid
|
|
*.seed
|
|
|
|
# Directory for instrumented libs generated by jscoverage/JSCover
|
|
lib-cov
|
|
|
|
# Coverage directory used by tools like istanbul
|
|
coverage
|
|
|
|
# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
|
|
.grunt
|
|
|
|
# Compiled binary addons (http://nodejs.org/api/addons.html)
|
|
build/Release
|
|
|
|
# Dependency directory
|
|
# 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
|
|
|
|
# Users Environment Variables
|
|
.lock-wscript
|