		@@ -91,3 +91,3 @@ var fork = require('child_process').fork

		cmd = opts.priorNodeArgs.concat(['-r', childHookPath]).concat(cmd)
		cmd = (opts.priorNodeArgs \|\| []).concat(['-r', childHookPath]).concat(cmd)
		log.debug('Starting child process %s', cmd.join(' '))
		@@ -94,0 +94,0 @@ child = fork(cmd[0], cmd.slice(1), {

package.json

		{
		"name": "ts-node-dev",
		"version": "1.0.0-pre.38",
		"version": "1.0.0-pre.39",
		"description": "Compiles your TS app and restarts when files are modified.",
		@@ -5,0 +5,0 @@ "keywords": [

README.md

		@@ -41,3 +41,3 @@ # ts-node-dev
		- `--ignore-watch` (default: []) - files/folders to be [ignored by `node-dev`](https://github.com/fgnass/node-dev#ignore-paths). But also this behaviour enhanced: it will also make up `new RegExp` of passed ignore string and check absolute paths of required files for match.
		So, to ignore everthing in `node_modules`, just pass `--ignore-watch node_modules`.
		So, to ignore everything in `node_modules`, just pass `--ignore-watch node_modules`.

		@@ -50,3 +50,3 @@ - `--debug` - some additional debug output.

		- Especially for large code bases always consider running with `--transpileOnly` flag which is normal for dev workflow and will speed up things greatly. Note, that `ts-node-dev` will not put watch handlers on TS files that contain only types/interfaces (used only for type checking) - this is current limitation by design.
		- Especially for large code bases always consider running with `--transpile-only` flag which is normal for dev workflow and will speed up things greatly. Note, that `ts-node-dev` will not put watch handlers on TS files that contain only types/interfaces (used only for type checking) - this is current limitation by design.

		@@ -63,4 +63,6 @@ - `--ignore-watch` will NOT affect files ignored by TS compilation. Use `--ignore` option (or `TS_NODE_IGNORE` env variable) to pass RegExp strings for filtering files that should not be compiled, by default `/node_modules/` are ignored.

		- In some rare cases `ts-node-dev` may fail to terminate an application by sending `SIGTERM` signal, this maybe caused by the app having running heavy child process or something. But the app should get the signal anyway and it can be explicitly processed there: `process.on('SIGTERM', () => process.exit())`.

		## License

		WTF.

ts-node-dev - npm Package Compare versions

Improved metrics