aboutsummaryrefslogtreecommitdiffstats
path: root/Node.gitignore
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' into patch-1Brendan Forster2018-06-171-0/+6
|\
| * Add .serverless to gitignoreTejas Shah2018-05-271-0/+3
| |
| * Add Vuepress build defalult output Directorysegayuu2018-05-251-0/+3
| |
* | Add exception for nuxt.js outputJefry Dewangga2018-05-061-0/+3
|/
* Update Node.gitignoregotonode2018-03-241-1/+1
|
* Update Node.gitignoreKyle Kelley2018-01-011-0/+2
|
* Node - update Compiled binary addons link to httpsRicky de Laveaga2017-08-311-1/+1
| | | | Node.gitignore build/Release Compiled binary addons: http to https https://nodejs.org/api/addons.html
* fix(Node): ignore yarn logsAnders D. Johnson2017-02-091-0/+2
| | | This adds ignores for the `yarn-debug.log*` and `yarn-error.log*` files sometimes produced by the [Yarn package manager](https://yarnpkg.com).
* added comment for typings directoryBrendan Forster2017-02-021-0/+2
|
* Merge branch 'master' into patch-3Brendan Forster2017-02-021-3/+16
|\
| * Merge pull request #2210 from mcandre/patch-1Brendan Forster2017-01-311-2/+2
| |\ | | | | | | [Node] make directory rules explicit
| | * fix gitignore syntaxAndrew Pennebaker2016-12-071-2/+2
| | | | | | | | | Some .gitignore parsers interpret directory vs non-directory patterns strictly (e.g. monochromegane/go-gitignore), so a `node_modules` pattern would not necessarily match against a real `node_modules` directory. It's generally safe to add a trailing slash to directory .gitignore patterns.
| * | Merge pull request #2157 from luiscoms/patch-1Brendan Forster2017-01-281-0/+3
| |\ \ | | | | | | | | Add bower dependency directory
| | * | Add bower dependency directoryLuis Fernando Gomes2016-10-281-0/+3
| | | |
| * | | Add .env to Node.gitignoreMalcolm2017-01-251-0/+3
| | |/ | |/|
| * | Add yarn ignored fileCraig Morris2016-10-121-0/+4
| |/
| * Update Node.gitignore (*.tgz)Mike Ralphson2016-09-261-0/+3
| | | | | | | | Add `*.tgz`, the output of `npm pack`, or other build-steps.
* | add typingsBen Bodenmiller2016-09-191-0/+1
|/
* Add eslint cache ignore for node projects.Kyle Pollock2016-08-191-0/+3
|
* Ignore *.pid.lockRoman Pushkin2016-07-021-0/+1
| | | | | | | | | Some popular applications (for example, Phusion Passenger) leave `*.pid.lock` file(s). For example, when you type `passenger start` with simple express app listening on port 3000, it leaves the following files: * `passenger.3000.pid` (removed when passenger stops) * `passenger.3000.log` * `passenger.3000.pid.lock` While `*pid` and `*.log` are ignored, `*.pid.lock` remains unignored. Phusion Passenger is quite popular, and `*.pid.lock` file should be ignored.
* Add nyc test coverage output directoryRoman Pushkin2016-04-211-0/+3
| | | [nyc](https://github.com/bcoe/nyc) is quite popular, and under some circumstances it writes to `.nyc_output` directory. This directory should be ignored by default.
* Merge Node.gitignore with masterMatti Jokitulppo2016-02-121-1/+6
|\
| * URL doesn't exists anymoreLevin Rickert2016-01-171-1/+0
| |
| * Ignore REPL history fileJulien CROUZET2015-11-051-0/+3
| | | | | | Like in #1732, Docker images can consider project directoy as $HOME
| * Add .npm cache directoryJulien CROUZET2015-11-021-0/+3
| |
* | Ignore JSPM package folderMatti Jokitulppo2015-10-121-1/+2
|/
* Add ignore for npm debug log filescyrbil2015-08-061-0/+1
|
* Fix typo from node_modules to node-modulesGoutham Veeramachaneni2015-04-301-1/+1
| | | Thanks to @arcresu for pointing out!
* Update npmjs docs linkGoutham Veeramachaneni2015-04-241-1/+1
| | | The previous link gives 404
* Update Node.gitignoreSebastian Blei2015-02-191-1/+1
| | | Corrected URL, which linked to the `Should I check my node_modules folder into git?` readup.
* Revert "Ignore npm-debug.log"Carl Suster2015-01-241-3/+0
|
* Ignore npm-debug.logJenrik2015-01-021-0/+3
| | | Debug log from npm is now ignored
* Merge pull request #1233 from stuartpb/patch-1Carl Suster2014-11-121-1/+0
|\ | | | | Restore original comment about node_modules
| * Let node_modules FAQ URL speak for itselfStuart P. Bentley2014-11-111-1/+0
| |
| * Restore original comment about node_modulesStuart P. Bentley2014-09-301-1/+1
| | | | | | | | | | | | | | | | 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.
* | Explain .lock-wscript and move itStuart P. Bentley2014-09-301-3/+3
|/ | | | | | | 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/
* Update Node.gitignoreJosh Whaley2014-08-131-1/+1
| | | Updated link for the dependency directory from [this](https://npmjs.org/doc/faq.html#Should-I-check-my-node_modules-folder-into-git) to [this](https://www.npmjs.org/doc/misc/npm-faq.html#should-i-check-my-node_modules-folder-into-git-).
* Adding .lock-wscriptScott J. Roberts2014-05-071-0/+3
|
* Reintroduce link to npmjscheddar2014-04-041-0/+2
| | | And remove my own opinions...
* Remove opinion from Node.js .gitignore filecheddar2014-04-041-2/+0
| | | | | This is a PR to remove the opinionated lines from the Node.js .gitignore file. I do not believe that Github's pre-baked .gitignore files should be promulgating opinions, especially in a community that is as fresh as the Node.js community. Questions of what should be checked in should be a decision made on an organization-by-organization basis, or left up to the individual. Github's inclusion of opinion in these files puts unnecessary authority behind that opinion, which can have the negative side-effect of people following without thinking.
* Remove Results classes from Node gitignoreStuart P. Bentley2014-02-281-7/+0
| | | These aren't really common patterns in the Node world, and if a Node project includes one of these types as files, they're as likely to want to include them in the project as not (`*.csv` is as likely to be a data source as `*.json`).
* Reduce commentsAdam Roben2014-02-281-18/+10
|
* Node.gitignore: correct term for instrumentationStuart P. Bentley2014-01-071-1/+1
|
* Add .grunt directoryStuart P. Bentley2014-01-071-1/+6
|
* Add `coverage` directory, rename coverage headingStuart P. Bentley2014-01-071-2/+5
|
* Add build/Release to Node gitignoreStuart P. Bentley2014-01-071-0/+3
| | | This re-covers the http://nodejs.org/api/addons.html case for which the "build" directory was added in 00686415c4, but doesn't break cross-environment projects that use the build directory for including concatenated/minified source. Mazel tov!
* Clarify node_modules commentStuart P. Bentley2014-01-071-2/+3
| | | Now linking to the official npm FAQ entry (with tl;dr) rather than straight to mikeal's blog post
* Refactor Node.gitignore with commentsStuart P. Bentley2014-01-021-7/+20
| | | | | | 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.
* add 'build' to Node.gitignoreRay Solomon2013-11-131-0/+1
| | | | | This is to exclude compiled code from nodejs addons. Reference: http://nodejs.org/api/addons.html
* remove `npm-debug.log` entryDan Kerimdzhanov2013-11-081-1/+0
|
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-03 16:16:53 +0000