e4e5da63fa
This changes the comment to better explain what .lock-wscript is for (it's for the [obsolete][v0.8.0] node-waf build system), and moves it next to the other ignore pattern(s) for binary module compilation artifacts. [v0.8.0]: http://blog.nodejs.org/2012/06/25/node-v0-8-0/
29 lines
582 B
Plaintext
29 lines
582 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
|
|
|
|
# node-waf configuration
|
|
.lock-wscript
|
|
|
|
# Compiled binary addons (http://nodejs.org/api/addons.html)
|
|
build/Release
|
|
|
|
# Dependency directory
|
|
# Commenting this out is preferred by some people, see
|
|
# https://www.npmjs.org/doc/misc/npm-faq.html#should-i-check-my-node_modules-folder-into-git-
|
|
node_modules
|