Loosing application output

[ColCh]

If I use grunt-nodemon, I loose application output. Wrong usage or real issue here?

output when using CLI:

myguestuser@360065e8fba2:/srv$ nodemon --ext js,jsx --ignore src,*.tmp,.git,.tmp/*,web_modules/*,.git/,node_modules/,bower_components/,.sass-cache/,Gruntfile.js,webpacconfig.js,webpack.dist.config.js,karma.conf.js,test --delay 800 --watch bin,lib,routes,.,models  bin/bootstrap.js 
18 Feb 20:12:59 - [nodemon] v1.3.7
18 Feb 20:12:59 - [nodemon] to restart at any time, enter `rs`
18 Feb 20:12:59 - [nodemon] watching: bin,lib,routes,.,models
18 Feb 20:12:59 - [nodemon] starting `node bin/bootstrap.js`
18 Feb 20:12:59 - [nodemon] watching 43,096 files - this might cause high cpu usage. To reduce use "--watch".
  express:application compile etag weak +0ms
  express:application compile query parser extended +2ms
  express:application compile trust proxy false +1ms
  express:application booting in development mode +0ms
Each child in an array should have a unique "key" prop. Check the renderComponent call using <Route>. See http://fb.me/react-warning-keys for more information.
express deprecated app.del: Use app.delete instead node_modules/express-namespace/index.js:58:16

And using grunt-nodemon:

myguestuser@360065e8fba2:/srv$ grunt nodemon
Running "nodemon:dev" (nodemon) task
[nodemon] v1.2.1
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: /srv/bin/**/* /srv/lib/**/* routes *.* /srv/models/**/*
[nodemon] starting `node bin/bootstrap.js`

grunt config:

    nodemon: {
      dev: {
        script: 'bin/bootstrap.js',
        options: {
          delay: 800,
          ext: "js,jsx",
          ignore: ["src", "*.tmp", ".git",".tmp/*", "web_modules/*", '.git/', 'node_modules/', 'bower_components/', '.sass-cache/', 'Gruntfile.js', 'webpack.config.js', 'webpack.dist.config.js', 'karma.conf.js', "test"],
          watch: ["bin", "lib", "routes", ".", "models"],
        }
      }
    },

[christopherdro]

Try configuring grunt-nodemon to use version 1.3.7 of nodemon instead of 1.2.1.

[ChrisWren]

Thanks for chiming in @christopherdro, gonna close based on that feedback.