No compatible version found: esprima

[bevacqua]

npm i react -S yields the following, in an empty repository.

npm ERR! notarget No compatible version found: esprima@'substack/esprima#is-keyword'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.7.0","0.8.0","0.8.1","0.8.2","0.9.0","0.9.1","0.9.2","0.9.3","0.9.4","0.9.5","0.9.6","0.9.7","0.9.8","0.9.9","1.0.0","1.0.1","1.0.2","1.0.3","1.0.4"]

[sophiebits]

What version of node and npm are you on?

[bevacqua]

λ node --version
v0.10.22
λ npm --version
1.3.23

[zpao]

Interesting... that branch definitely exists in substack's repo. Not much for us to do at this point except switch to using envify.next (already doing that in trunk).

[yanns]

Is there any workaround at the moment?

[zpao]

Work around is to publish a new React package with an update to envify. (or modify your installed react package to use a different version).

[MattKunze]

The chance of an official 0.8.1 version or similar that does this is... greater than zero? :)

[MattKunze]

nm - this has started working for me at least, the upstream version issue with esprima must have changed

[yanns]

@MattKunze which version do you use?
Still no improvement for me, quite a blocker...

[yanns]

@zpao I cannot modify my installed react package, as I cannot install react at all.

[yanns]

For info: the version 0.9.0-rc1 fixes this problem.

[MattKunze]

Yeah, that's working for me as well (sorry I didn't get back about your initial question, I was traveling over the weekend).

I think the issue for us had to do with having envify as a dependency as well, since it also depends on esprima.

[zerkalica]

Works for 0.9.0-rc1, but invalid version error for 0.9.0

node --version
v0.10.15

npm -v
1.2.18

npm install react@0.9.0

...
npm ERR! Error: invalid version: 3001.0001.0000-dev-harmony-fb
npm ERR!     at validVersion (/usr/lib/nodejs/read-package-json/read-json.js:573:40)

Same error for reactify

[zpao]

I guess semver parsing changed. It's being parsed fine now as 3001.1.0-dev-harmony-fb. fwiw, npm 1.2.18 is ~1 year old, so I would suggest updating. I guess we could actually publish our version numbers there differently too.

[sophiebits]

Closing this out as every instance of this that I've seen has been fixed by upgrading npm.

[shaunol]

Commenting in this issue because it was the first result on Google when I had the exact problem just now, even with the latest version of npm.

My particular issue was that I didn't have git installed. I installed git, restarted cmd and "npm install" now works correctly.

Thanks to terinjokes in #reactjs