nodemon -v
:nodemon -v
1.13.3
node -v
:node -v
v8.9.3
Heiko-MacPro:ms-fileservice-ts heiko$ npm start
> @hke/[email protected] start /Users/heiko/Sites/ms-fileservice-ts
> nodemon
[nodemon] 1.13.3
[nodemon] reading config /Users/heiko/Sites/ms-fileservice-ts/package.json
[nodemon] to restart at any time, enter `rs`
[nodemon] or send SIGHUP to 2834 to restart
[nodemon] ignoring: /Users/heiko/dev/ms-fileservice-ts/.git/**/* .nyc_output .sass-cache bower_components coverage /Users/heiko/dev/ms-fileservice-ts/node_modules/**/* build/compiled.js package.json
[nodemon] watching: /Users/heiko/Sites/ms-fileservice-ts/server/**/* /Users/heiko/Sites/ms-fileservice-ts/services/**/* app.ts
[nodemon] watching extensions: js,json
[nodemon] starting `npm run dev`
[nodemon] child pid: 2836
[nodemon] watching 6 files
> @hke/[email protected] dev /Users/heiko/Sites/ms-fileservice-ts
> npm run build && node build/compiled.js
> @hke/[email protected] build /Users/heiko/Sites/ms-fileservice-ts
> webpack --config config/webpack.config.js
ts-loader: Using [email protected] and /Users/heiko/Sites/ms-fileservice-ts/tsconfig.json
Hash: dfaa5ded6ecec74e4e71
Version: webpack 1.13.2
Time: 2458ms
Asset Size Chunks Chunk Names
compiled.js 20.9 kB 0 [emitted] main
+ 20 hidden modules
ab
Listening on port 3300
[nodemon] files triggering change check: services/file.service.ts
[nodemon] matched rule: **/Users/heiko/Sites/ms-fileservice-ts/services/**/*
[nodemon] changes after filters (before/after): 1/0
nodemonConfig in package.json:
"nodemonConfig": {
"verbose": true,
"env": {
"env": "development",
"DEBUG": "modern-express:*"
},
"exec": "npm run dev",
"execMap": {
"ts": "npm run dev"
},
"ignore": [
"build/compiled.js",
"package.json"
],
"watch": [
"server",
"services",
"app.ts"
]
}
My npm scripts:
"build": "webpack --config config/webpack.config.js",
"start": "nodemon",
"dev": "npm run build && node build/compiled.js",
Nodemon should restart the build and my application
Recognizes the file change but does not restart. When I enter rs
it does what it should.
I can make that repo public this evening if it helps.
If applicable, please append the --dump
flag on your command and include the output here **ensuring to remove any sensitive/personal details or tokens.
> nodemon --dump
[nodemon] 1.13.3
[nodemon] reading config /Users/heiko/dev/ms-fileservice-ts/package.json
[nodemon] to restart at any time, enter `rs`
[nodemon] or send SIGHUP to 3010 to restart
[nodemon] ignoring: /Users/heiko/dev/ms-fileservice-ts/.git/**/* .nyc_output .sass-cache bower_components coverage /Users/heiko/dev/ms-fileservice-ts/node_modules/**/* build/compiled.js package.json
[nodemon] watching: /Users/heiko/Sites/ms-fileservice-ts/server/**/* /Users/heiko/dev/ms-fileservice-ts/services/**/* app.ts
[nodemon] watching extensions: js,json
--------------
node: v8.9.3
nodemon: 1.13.3
command: /Users/heiko/.nvm/versions/node/v8.9.3/bin/node /Users/heiko/dev/ms-fileservice-ts/node_modules/.bin/nodemon --dump
cwd: /Users/heiko/Sites/ms-fileservice-ts
OS: darwin x64
--------------
{ run: false,
system: { cwd: '/Users/heiko/Sites/ms-fileservice-ts' },
required: false,
dirs:
[ '/Users/heiko/Sites/ms-fileservice-ts/server',
'/Users/heiko/Sites/ms-fileservice-ts/services',
'/Users/heiko/Sites/ms-fileservice-ts/app.ts' ],
timeout: 1000,
options:
{ dump: true,
verbose: true,
env: { env: 'development', DEBUG: 'modern-express:*' },
exec: 'npm run dev',
execMap: { ts: 'npm run dev', py: 'python', rb: 'ruby' },
ignore:
[ '.git',
'.nyc_output',
'.sass-cache',
'bower_components',
'coverage',
'node_modules',
'build/compiled.js',
'package.json',
re: /\.git|\.nyc_output|\.sass\-cache|bower_components|coverage|node_modules|build\/compiled\.js|package\.json/ ],
watch: [ 'server', 'services', 'app.ts', re: /server|services|app\.ts/ ],
ignoreRoot:
[ '.git',
'.nyc_output',
'.sass-cache',
'bower_components',
'coverage',
'node_modules' ],
restartable: 'rs',
colours: true,
stdin: true,
runOnChangeOnly: false,
signal: 'SIGUSR2',
stdout: true,
watchOptions: {},
execOptions:
{ script: null,
exec: 'npm run dev',
args: [],
scriptPosition: null,
nodeArgs: undefined,
execArgs: [],
ext: 'js,json',
env: { env: 'development', DEBUG: 'modern-express:*' } },
monitor:
[ '/Users/heiko/dev/ms-fileservice-ts/server/**/*',
'/Users/heiko/dev/ms-fileservice-ts/services/**/*',
'app.ts',
'!/Users/heiko/dev/ms-fileservice-ts/.git/**/*',
'!.nyc_output',
'!.sass-cache',
'!bower_components',
'!coverage',
'!/Users/heiko/dev/ms-fileservice-ts/node_modules/**/*',
'!build/compiled.js',
'!package.json' ] },
load: [Function],
reset: [Function: reset],
lastStarted: 0,
loaded: [ '/Users/heiko/dev/ms-fileservice-ts/package.json' ],
watchInterval: null,
signal: 'SIGUSR2',
command:
{ raw: { executable: 'npm run dev', args: [] },
string: 'npm run dev' } }
--------------
[nodemon] exiting
Acknowledging this bug. I've seen this [nodemon] matched rule: **/Users/heiko/Sites/ms-fileservice-ts/services/**/*
be a problem in another issue - specifically the leading **/
part. Will try to ship a fix as part of today's releases.
Unfortunately its not fixed completely. I added my project here: https://github.com/hkeio/fileservice
To reproduce clone and run npm i && npm start
.
If you change something in app.ts
it works fine. Changing something in service/file.service.ts
does not. At startup it shows:
[nodemon] watching: /Users/heiko/Sites/ms-fileservice-ts/bin/**/* /Users/heiko/Sites/ms-fileservice-ts/classes/**/* /Users/heiko/Sites/ms-fileservice-ts/server/**/* /Users/heiko/Sites/ms-fileservice-ts/services/**/* app.ts
On changing the file it still shows the leading **/
nodemon] files triggering change check: services/file.service.ts
[nodemon] matched rule: **/Users/heiko/Sites/ms-fileservice-ts/services/**/*
[nodemon] changes after filters (before/after): 1/0
I'm not sure this is relevant but the verbose output clued me in that I needed to also watch .ts files. This is the verbose output:
[nodemon] watching extensions: js,json
So I added -e js,json,ts
as an argument to nodemon and now changes in ts files immediately trigger a rebuild.
Most helpful comment
I'm not sure this is relevant but the verbose output clued me in that I needed to also watch .ts files. This is the verbose output:
So I added
-e js,json,ts
as an argument to nodemon and now changes in ts files immediately trigger a rebuild.