srizan/archived-nodemon
1
0
Fork 0
mirror of https://github.com/SrIzan10/nodemon.git synced 2026-05-01 10:55:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' into fix/456

Browse Source 
Conflicts:
	faq.md
This commit is contained in:
Remy Sharp
2015-01-28 15:03:42 +00:00
parent aa755af0aa f4866fbf8e
commit 3deef004fe
2 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -236,6 +236,10 @@ Check out the [gulp-nodemon](https://github.com/JacksonGariety/gulp-nodemon) plu
Check out the [grunt-nodemon](https://github.com/ChrisWren/grunt-nodemon) plugin to integrate nodemon with the rest of your project's grunt workflow.
## FAQ
See the [FAQ](https://github.com/remy/nodemon/blob/master/faq.md) and please add your own questions if you think they would help others.
# License
MIT [http://rem.mit-license.org](http://rem.mit-license.org)

9
faq.md
View File

@@ -128,4 +128,11 @@ For example, on `lib/app.js` being changed:
The new `nodemon.json` superceeds the `.nodemonignore` file, so if you have both, the `.nodemonignore` is not used at all.
Note that if you have a `nodemon.json` in your `$HOME` path, then this will also superceed the old ignore file.
Note that if you have a `nodemon.json` in your `$HOME` path, then this will also superceed the old ignore file.
## nodemon does nothing
On Ubuntu globally installed node applications have been found to have no output when they're run. This *seems* to be an issue with node not being correctly installed (possibly linked to the binary having to be called `nodejs`).
The solution (that's worked in the past) is to install [nvm](https://github.com/creationix/nvm) first and using it to install node, *rather* than using `apt-get` (or similar tools) to install node directly.
>>>>>>> master