Installing >v5.0.0 with node v0.10 errors on eslint

[maxbeatty]

When installing standard at any version above 5.0.0 using node v0.10.40, an error occurs. Here is a sample travis job failing to install "^5.3.0". Travis passes when we explicitly set "5.0.0".

As a maintainer of dotenv, I'd like to continue supporting v0.10 like the LTS plan lays out. Is there anything we can do besides stay with 5.0.0?

[dcousens]

@maxbeatty this seems very odd, I'm sure we'll be able to find the reason and allow you to use ^5.3.0.

[feross]

This issue will be fixed soon (hopefully within 24 hours) when eslint publishes a new version. The issue is caused by standard-engine depending on a package from GitHub, to get a bug fix that hasn't been published yet. See: https://github.com/Flet/standard-engine/blob/master/package.json#L13

[watson]

@feross is there anything I can do to help with this?

[watson]

Hmm... this actually seems to affect all versions of Node - not just 0.10.x: https://travis-ci.org/watson/async-state/builds/81012276

[watson]

My bad - it's not related to the version of Node, but the version of npm. I've made a pull request in standard-engine that should fix it: standard/standard-engine#15

[watson]

@maxbeatty The issue with standard-engine not being able to install with older versions of npm have been fixed now in v2.1.1. If you reinstall standard it should automatically fetch the new version of standard-engine and everything should work again

[Flet]

@watson Nice! Thanks!

[ginman86]

I'm getting a similar error on eslint, just tried. 5.0.0 does work.

A786391-DEN-OEM:client-generator A786391$ npm install standard --save-dev
npm ERR! fetch failed https://github.com/eslint/eslint.git#9d6223040316456557e0a2383afd96be90d28c5a
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 406

[maxbeatty]

Thanks everyone for your help! I re-ran the build and everything is working again ✅

[watson]

@ginman86 weird - can I get you to run npm --version to see what version of npm you have?

[ginman86]

@watson just confirmed this is working after your PR was merged. It must not have been published yet when i was trying. Thanks for the followup.

[watson]

👍

[feross]

Thanks for your help @watson – I've added you as a GitHub collaborator and npm owner 👍

Also, eslint 1.5.0 was published earlier today, so I've removed the git dependency entirely, as promised. Sorry for the trouble, everyone.