Hey, I've started using (and loving) MERN stack on a new app that I've been tasked with developing, have been focussing mostly on front end up until today and it has been great!. It's currently taking 2-3 minutes to start or restart the nodemon task (via npm run start) which is pretty frustrating while I'm trying to get authentication right and having to constantly wait..

Is this a normal experience or something particular in my env??

I'm on a 2014 macbook air running Sierra and havent experienced issues with gulp, grunt or nodemon in the past, this is my first experience with webpack and isomorphic though...

-edit-

It may be worth noting that I get the child processes triggering on every change, example below:

[nodemon] files triggering change check: server/routes/User.routes.js
[nodemon] matched rule: **/Users/nicky/Sites/isw-contacts/server/**/*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] server/routes/User.routes.js

[nodemon] starting `node index.js`
[nodemon] child pid: 69369
[nodemon] files triggering change check: server/routes/User.routes.js
[nodemon] matched rule: **/Users/nicky/Sites/isw-contacts/server/**/*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] server/routes/User.routes.js

[nodemon] starting `node index.js`
[nodemon] child pid: 69372
[nodemon] files triggering change check: server/routes/User.routes.js
[nodemon] matched rule: **/Users/nicky/Sites/isw-contacts/server/**/*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] server/routes/User.routes.js

[nodemon] starting `node index.js`
[nodemon] child pid: 69375