reid / node-jslint

The JavaScript Code Quality Tool — for Node.js.
http://jslint.com/
Other
491 stars 101 forks source link

error installing with npm #96

Closed eurekaa closed 9 years ago

eurekaa commented 10 years ago

Hi, i got an error with your package dependecies, npm doesn't find compatible versions.

I solved updating nodejs, maybe my npm version did'nt support a dependency definition like 'glob@^4.0.4' (maybe the ^ char?).

I report this just for information. My environment version before the update was: node: 0.10.9 npm: 1.2.24

Thanks.

smikes commented 10 years ago

Thanks for the bug report. It sounds like you have worked around it for now, but I'm sorry to hear you had trouble.

I will review the dependencies that we require -- I believe we require node 0.10, but some of our dependencies may require a specific patchlevel for the engine.

okuryu commented 10 years ago

I confirmed reproducing fails installing the package with Node.js 0.10.9 and npm 1.2.24, but I would like to recommend to using latest Node.js and npm.

smikes commented 10 years ago

I am not sure which package was causing the problem; we ourselves require node >= 0.10.0, but that should not cause a problem.

Closing because "I report this just for information"

smikes commented 10 years ago

"Just note that you need npm 1.3 or later (introduced in node 0.10.13) to install a module that uses this operator." from http://www.jakobm.com/semver-in-nodejs-and-npm

eurekaa commented 10 years ago

Yeah i thought it was the ^ operator! damn it! :) The errors appears for every dependency defined with it. I solved quickly with an update but it's quite difficult to understand and many people should decide to leave the package for another one, that should be a pity. Just for your info anyway. Thanks for your kind response. Stefano

eurekaa commented 10 years ago

In your package.json the engine dependency is node 0.10.0. It should be 0.10.13.

I added it to my projects too. Thanks for the trick ;)

smikes commented 10 years ago

Good point. I will fix it.

smikes commented 9 years ago

Actually, revisiting this, this is an npm dependency not a node dependency (since npm@2.7.3 will run on node >= 0.8). So I will not adjust the engines parameter, but I will update the documentation.