Get very old version under node 0.8.0 about node-supervisor HOT 5 CLOSED

Seems that the latest version doesn't like 0.8

npm install [email protected]
npm ERR! notsup Required: {"node":"~0.3.7 || 0.4 || 0.5 || 0.6 || 0.7"}
npm ERR! notsup Actual:   {"npm":"1.1.32","node":"0.8.0"}

from node-supervisor.

Yep, my bad. It didn't support 0.8 because 0.8 didn't exist until just recently. v0.3.6 is now released.

from node-supervisor.

It's still rejecting node 0.8.0 for me. Common practice seems to be only restricting older versions (">=0.3.7") or leave engines out entirely. Taking a chance on the latest node version is probably better than reverting to supervisor version 0.0.6!

PS C:> npm install -g [email protected]
npm http GET https://registry.npmjs.org/supervisor/0.3.6
npm http 304 https://registry.npmjs.org/supervisor/0.3.6
npm ERR! notsup Unsupported
npm ERR! notsup Not compatible with your version of node/npm: [email protected]
npm ERR! notsup Required: {"node":">=0.3.7 <=0.8"}
npm ERR! notsup Actual: {"npm":"1.1.32","node":"0.8.0"}

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js"
"install" "-g" "[email protected]"
npm ERR! cwd C:
npm ERR! node -v v0.8.0
npm ERR! npm -v 1.1.32
npm ERR! code ENOTSUP
npm ERR! message Unsupported
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\npm-debug.log
npm ERR! not ok code 0

from node-supervisor.

Ah, how silly of me. 0.4.1 should have an actually useful engine declaration.

My ideal behavior would be that npm refused to install any version until the compatibility is updated. It's only installing an old version because that very old package was published without an upper bound.

It's a fair point about leaving the top unbounded - maybe I'll either do that, or just unpublish the very old versions.

from node-supervisor.

Ok, more thought and this discussion convinced me to drop the upper limit.

from node-supervisor.