Incorrect warning about engineStrict

[mgol]

$ npm --version
2.7.0
$ node --version
v1.4.1
$ npm -g i npm-bump                                                                   
npm WARN engineStrict Per-package engineStrict (found in package.json for npm-bump)
npm WARN engineStrict won't be used in npm 3+. Use the config setting `engine-strict` instead.
/Users/mgol/.nvm/versions/io.js/v1.4.1/bin/npm-bump -> /Users/mgol/.nvm/versions/io.js/v1.4.1/lib/node_modules/npm-bump/bin/npm-bump
[email protected] /Users/mgol/.nvm/versions/io.js/v1.4.1/lib/node_modules/npm-bump
├── [email protected]
├── [email protected] ([email protected], [email protected], [email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])

The problem is there's no engineStrict in npm-bump's package.json. ;) It used to be there but I removed it. I've checked after the installation:

$ cat ~/.nvm/versions/io.js/v1.4.1/lib/node_modules/npm-bump/package.json | grep engine
  "engines": {

[smikes]

That's a really cool bug.

Added:
By the way, I was able to trigger the message, but I didn't figure out how it happened.

[othiym23]

This was a surprisingly tricky bug to address, but I ultimately realized that this warning, like many others, is really only useful to package maintainers. That means you only care about engineStrict in the current top-level package.json, so I added a post-install validation check for exactly that. Landed as b6bd99a. Thanks for filing this, @mzgol!

[aa6my]

my error output like this. how to fix it?

npm WARN engineStrict Per-package engineStrict (found in package.json for cordova)
npm WARN engineStrict won't be used in npm 3+. Use the config setting engine-strict instead.
npm WARN engine [email protected]: wanted: {"node":">=0.6","npm":"1"} (current: {"node":"0.12.0","npm":"2.7.0"})
npm WARN engine [email protected]: wanted: {"node":"~0.10.x"} (current: {"node":"0.12.0","npm":"2.7.0"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x || 0.10.x"} (current: {"node":"0.12.0","npm":"2.7.0"})

[kenany]

@aa6my I don't see an error in the log you've posted. I just see a few warnings, which in many cases can usually be ignored without consequences.

[othiym23]

Plus I tweaked that behavior some more in [email protected] to only warn for the current package, not child dependencies. So when you upgrade again after 2.7.1 is out of testing, you'll stop getting the engineStrict warning.