parallaxis/node_modules/nodemon/package.json

72 lines
11 KiB
JSON
Raw Permalink Normal View History

{
"name": "nodemon",
"homepage": "http://nodemon.io",
"author": {
"name": "Remy Sharp",
"url": "http://github.com/remy"
},
"contributors": [
{
"name": "Michael Hueuberger",
"email": "michael.heuberger@binarykitchen.com"
}
],
"bin": {
"nodemon": "./bin/nodemon.js"
},
"engines": {
"node": ">=0.8"
},
"repository": {
"type": "git",
"url": "http://github.com/remy/nodemon.git"
},
"description": "Simple monitor script for use during development of a node.js app.",
"keywords": [
"monitor",
"development",
"restart",
"autoload",
"reload",
"terminal"
],
"version": "1.2.0",
"preferGlobal": "true",
"licenses": [
{
"type": "MIT",
"url": "http://rem.mit-license.org"
}
],
"main": "./lib/nodemon",
"scripts": {
"coverage": "istanbul cover _mocha -- --timeout 30000 --ui bdd --reporter list test/**/*.test.js",
"test": "node_modules/mocha/bin/_mocha --timeout 30000 --ui bdd test/**/*.test.js",
"web": "node web"
},
"devDependencies": {
"connect": "~2.19.1",
"mocha": "~1.20.0",
"should": "~4.0.0",
"istanbul": "~0.2.10",
"touch": "~0.0.3",
"coffee-script": "~1.7.1"
},
"dependencies": {
"update-notifier": "~0.1.8",
"minimatch": "~0.3.0",
"ps-tree": "~0.0.3"
},
"readme": "![nodemon logo](http://nodemon.io/nodemon.png)\n\n# nodemon\n\n[![Flattr this](http://api.flattr.com/button/flattr-badge-large.png)](http://flattr.com/thing/1211372/remynodemon-on-GitHub)\n\nFor use during development of a node.js based application.\n\nnodemon will watch the files in the directory that nodemon was started, and if they change, it will automatically restart your node application.\n\nnodemon does **not** require *any* changes to your code or method of development. nodemon simply wraps your node application and keeps an eye on any files that have changed. Remember that nodemon is a replacement wrapper for `node`, think of it as replacing the word \"node\" on the command line when you run your script.\n\n[![NPM version](https://badge.fury.io/js/nodemon.svg)](http://badge.fury.io/js/nodemon)\n[![Travis Status](https://travis-ci.org/remy/nodemon.svg)](https://travis-ci.org/remy/nodemon)\n\n# Installation\n\nEither through forking or by using [npm](http://npmjs.org) (the recommended way):\n\n npm install -g nodemon\n\nAnd nodemon will be installed in to your bin path. Note that as of npm v1, you must explicitly tell npm to install globally as nodemon is a command line utility.\n\n# Usage\n\nnodemon wraps your application, so you can pass all the arguments you would normally pass to your app:\n\n nodemon [your node app]\n\nFor example, if my application accepted a host and port as the arguments, I would start it as so:\n\n nodemon ./server.js localhost 8080\n\nAny output from this script is prefixed with `[nodemon]`, otherwise all output from your application, errors included, will be echoed out as expected.\n\nnodemon also supports running and monitoring [coffee-script](http://jashkenas.github.com/coffee-script/) apps:\n\n nodemon server.coffee\n\nIf no script is given, nodemon will test for a `package.json` file and if found, will run the file associated with the *main* property ([ref](https://github.com/remy/nodemon/issues/14)).\n\nYou can also pass the debug flag to node through the command line as you would normally:\n\n nodemon --debug ./server.js 80\n\nIf you have a `package.json` file for your app, you can omit the main script entirely and nodemon will read the `package.json` for the `main` property and use that value as the app.\n\nnodemon will also search for the `scripts.start` property in `package.json` (as of nodemon 1.1.x).\n\nAlso check out the [FAQ](https://github.com/remy/nodemon/blob/master/faq.md) or [issues](https://github.com/remy/nodemon/issues) for nodemon.\n\n## Automatic re-running\n\nnodemon was original written to restart hanging processes such as web servers, but now supports apps that cleanly exit. If your script exits cleanly, nodemon will continue to monitor the directory (or directories) and restart the script if there are any changes.\n\n## Manual restarting\n\nWhilst nodemon is running, if you need to manually restart your application, instead of stopping and restart nodemon, you can simply type `rs` with a carriage return, and nodemon will restart your process.\n\n## Config files\n\nnodemon supports local and global configuration files. These are named `nodemon.json` and can be located in the current working directory or in your home directory.\n\nThe specificity is as follows, so that a command line argument will always override the config file settings:\n\n- command line arguments\n- local config\n- global config\n\nA config file can take any of the command line arguments as JSON key values, for example:\n\n {\n \"verbose\": true,\n \"ignore\": [\"*.test.js\", \"fixtures/*\"],\n \"execMap\": {\n \"rb\": \"ruby\",\n \"pde\": \"processing --sketch={{pwd}} --run\"\n }\n }\n\nThe above `nodemon.json` file might be my global config so that I have support for ruby files and processing files, and I can simply run `nodemon demo.pde` and nodemon will automatically know how to run the script even though out of the box support for processing scripts.\n\nA further example of options can be seen in [sample-nodemon.md](htt
"readmeFilename": "README.md",
"bugs": {
"url": "https://github.com/remy/nodemon/issues"
},
"_id": "nodemon@1.2.0",
"dist": {
"shasum": "18c752c515b7d58d452b51ada68185556e12e4b6"
},
"_from": "nodemon@",
"_resolved": "https://registry.npmjs.org/nodemon/-/nodemon-1.2.0.tgz"
}