albertosantini
commented
9 years ago The package is installed correctly.
That is only a npm warning.
$ npm install rio
npm WARN engine rio@1.4.0: wanted: {"node":"~0.10.x"} (current: {"node":"4.1.2","npm":"2.14.4"})
rio@1.4.0 node_modules\rio
├── hexy@0.2.7
└── binary@0.3.0 (buffers@0.1.1, chainsaw@0.1.0)
$ node
> var rio = require("rio")
var rio = require("rio")
undefined
> rio
{ enableDebug: [Function: enableDebug],
enableRecordMode: [Function: enableRecordMode],
enablePlaybackMode: [Function: enablePlaybackMode],
evaluate: [Function: evaluate],
shutdown: [Function: shutdown],
sourceAndEval: [Function: sourceAndEval],
bufferAndEval: [Function: bufferAndEval] }
> In release 2.x the engine property will be handled better.
P.S.: it would be enough "node": ">=0.10.x" to shut up the warning, but I change that in dev branch.
https://github.com/albertosantini/node-rio/commit/523c4855b04a4252c97793ee43c78940a57e0a54
I get:
'npm WARN engine rio@1.4.0: wanted: {"node":"~0.10.x"} (current: {"node":"4.1.2","npm":"2.14.4"})'
I assume the error is because rio hasn't been update to reflect the new node versioning scheme? Is there any way I can work around it? Or can you please update so it works with the current version of node?
Thank you!