> [email protected] prestart /Users/aldon/Code/Dev-Environment-Template
> node buildScripts/startMessage.js

Starting app in dev mode...

> [email protected] start /Users/aldon/Code/Dev-Environment-Template
> npm-run-all --parallel security-check open:src


> [email protected] security-check /Users/aldon/Code/Dev-Environment-Template
> nsp check


> [email protected] open:src /Users/aldon/Code/Dev-Environment-Template
> node buildScripts/srcServer.js

(+) 1 vulnerabilities found
┌───────────────┬───────────────────────────────────────────────────────┐
│               │ Regular Expression Denial of Service                  │
├───────────────┼───────────────────────────────────────────────────────┤
│ Name          │ debug                                                 │
├───────────────┼───────────────────────────────────────────────────────┤
│ Installed     │ 2.6.8                                                 │
├───────────────┼───────────────────────────────────────────────────────┤
│ Vulnerable    │ <= 2.6.8 || >= 3.0.0 <= 3.0.1                         │
├───────────────┼───────────────────────────────────────────────────────┤
│ Patched       │ >= 2.6.9 < 3.0.0 || >= 3.1.0                          │
├───────────────┼───────────────────────────────────────────────────────┤
│ Path          │ [email protected] > [email protected] > [email protected]      │
├───────────────┼───────────────────────────────────────────────────────┤
│ More Info     │ https://nodesecurity.io/advisories/534                │
└───────────────┴───────────────────────────────────────────────────────┘

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] security-check: `nsp check`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] security-check script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/aldon/.npm/_logs/2018-01-25T05_03_21_346Z-debug.log
ERROR: "security-check" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `npm-run-all --parallel security-check open:src`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/aldon/.npm/_logs/2018-01-25T05_03_21_418Z-debug.log

"babel-cli": "6.16.0",
"babel-core": "6.17.0",
"babel-loader": "6.2.5",
"babel-preset-latest": "6.16.0",
"babel-register": "6.16.3",

Dev-Environment-Template git:(10-transpiling-setup) npm install
npm WARN deprecated [email protected]: We're super 😸  excited that you're trying to use ES2017+ syntax, but instead of making more yearly presets 😭 , Babel now has a better preset that we recommend you use instead: npm install babel-preset-env --save-dev. preset-env without options will compile ES2015+ down to ES5 just like using all the presets together and thus is more future proof. It also allows you to target specific browsers so that Babel can do less work and you can ship native ES2015+ to user 😎 ! We are also in the process of releasing v7, so please give http://babeljs.io/blog/2017/09/12/planning-for-7.0 a read and help test it out in beta! Thanks so much for using Babel 🙏, please give us a follow on Twitter @babeljs for news on Babel, join slack.babeljs.io for discussion/development and help support the project at opencollective.com/babel
npm WARN deprecated [email protected]: We're super 😸  excited that you're trying to use ES2017 syntax, but instead of making more yearly presets 😭 , Babel now has a better preset that we recommend you use instead: npm install babel-preset-env --save-dev. preset-env without options will compile ES2015+ down to ES5 just like using all the presets together and thus is more future proof. It also allows you to target specific browsers so that Babel can do less work and you can ship native ES2015+ to user 😎 ! We are also in the process of releasing v7, so please give http://babeljs.io/blog/2017/09/12/planning-for-7.0 a read and help test it out in beta! Thanks so much for using Babel 🙏, please give us a follow on Twitter @babeljs for news on Babel, join slack.babeljs.io for discussion/development and help support the project at opencollective.com/babel
npm WARN deprecated [email protected]: We're super 😸  excited that you're trying to use ES2016 syntax, but instead of making more yearly presets 😭 , Babel now has a better preset that we recommend you use instead: npm install babel-preset-env --save-dev. preset-env without options will compile ES2015+ down to ES5 just like using all the presets together and thus is more future proof. It also allows you to target specific browsers so that Babel can do less work and you can ship native ES2015+ to user 😎 ! We are also in the process of releasing v7, so please give http://babeljs.io/blog/2017/09/12/planning-for-7.0 a read and help test it out in beta! Thanks so much for using Babel 🙏, please give us a follow on Twitter @babeljs for news on Babel, join slack.babeljs.io for discussion/development and help support the project at opencollective.com/babel
npm WARN deprecated [email protected]: We're super 😸  excited that you're trying to use ES2015 syntax, but instead of making more yearly presets 😭 , Babel now has a better preset that we recommend you use instead: npm install babel-preset-env --save-dev. preset-env without options will compile ES2015+ down to ES5 just like using all the presets together and thus is more future proof. It also allows you to target specific browsers so that Babel can do less work and you can ship native ES2015+ to user 😎 ! We are also in the process of releasing v7, so please give http://babeljs.io/blog/2017/09/12/planning-for-7.0 a read and help test it out in beta! Thanks so much for using Babel 🙏, please give us a follow on Twitter @babeljs for news on Babel, join slack.babeljs.io for discussion/development and help support the project at opencollective.com/babel

> [email protected] install /Users/aldon/Code/Dev-Environment-Template/node_modules/fsevents
> node install

[fsevents] Success: "/Users/aldon/Code/Dev-Environment-Template/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN [email protected] requires a peer of webpack@1 || ^2.1.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] No repository field.

> [email protected] lint /Users/aldon/Code/Dev-Environment-Template
> esw webpack.config.* src buildScripts --color

/Users/aldon/Code/Dev-Environment-Template/src/index.js (1/1)
  ✖  5:1  Unexpected 'debugger' statement  no-debugger
  !  6:1  Unexpected console statement     no-console

/Users/aldon/Code/Dev-Environment-Template/buildScripts/srcServer.js (0/1)
  !  22:5  Unexpected console statement  no-console

/Users/aldon/Code/Dev-Environment-Template/buildScripts/startMessage.js (0/1)
  !  3:1  Unexpected console statement  no-console

✖ 1 error ! 3 warnings (13:45:25)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] lint: `esw webpack.config.* src buildScripts --color`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/aldon/.npm/_logs/2018-02-14T19_45_25_441Z-debug.log