This restructures the NodeJS gitignore to include comments explaining under what category each pattern is excluded, including a note that node_modules should sometimes not be gitignored as a Node convention.
The "build" directory is lost in this refactor, as many JS projects do wish to include a minified/concatenated version of their source in the "build" folder in source control.
Refactor Node.gitignore with comments
The "build" directory is lost in this refactor, as many JS projects
do wish to include a minified/concatenated version of their source
in the "build" folder in source control.
Thanks for the cleanup! It's super-helpful.
Unfortunately I merged some other changes to this file before I got to your PR. Could you update your branch to bring them into your great new organization?
Clarify node_modules comment
Now linking to the official npm FAQ entry (with tl;dr) rather than straight to mikeal's blog post
Add build/Release to Node gitignore
This re-covers the http://nodejs.org/api/addons.html case for which the "build" directory was added in 0068641, but doesn't break cross-environment projects that use the build directory for including concatenated/minified source. Mazel tov!
Add `coverage` directory, rename coverage heading
Add .grunt directory
Ignore grunt and lcov build files in Node projects
I've implemented some more commits that implement / supersede the intervening changes.
Node.gitignore: correct term for instrumentation
Sorry, but this PR's outdated again. Could you bring it up to date so that it's mergeable? Also I would suggest removing your heading comments (starting with #) since they don't add a lot and make the file harder to read. The other comments (with ## changed to #), however, are helpful, so thanks for that!
I cleaned this up myself instead of making @stuartpb go through another round just because I missed his fixups last time.