Keystone-classic: npm install error on master

[liming]

After upgrade react.js recently. npm install error.

npm ERR! peerinvalid The package react does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants react@^0.14.0 || ^15.0.0
npm ERR! peerinvalid Peer [email protected] wants react@^15.0.1
npm ERR! peerinvalid Peer [email protected] wants react@>=0.12.0
npm ERR! peerinvalid Peer [email protected] wants react@^0.14.0
npm ERR! peerinvalid Peer [email protected] wants react@~0.13.x || ~0.14.x || ^15.0.0
npm ERR! peerinvalid Peer [email protected] wants react@^0.14.0 || ^15.0.0-0
npm ERR! peerinvalid Peer [email protected] wants react@^15.0.1
npm ERR! peerinvalid Peer [email protected] wants react@^0.14 || ^15.0.0-rc || ^15.0.0

[JedWatson]

Totally aware of this, I updated react without considering how much npm was going to whinge about it 😁

Not much we can do but wait for all those dependencies to update their peer deps, hopefully won't take long. I've fixed the ones I'm responsible for!

[mxstbr]

Closing this issue as there's nothing actionable for us left to do here. Sorry about the problems, there's nothing we can do from our side except wait!

[liming]

@JedWatson and @mxstbr , just want to ask, is there any workaround? It's really bother me because heroku deploy need npm install every time so I cannot deploy my latest implementation for about 2 weeks.

[JedWatson]

I think I'm just going to fork react-color... 😞

[liming]

Forked react-color and keystonejs to work around this problem.

[morenoh149]

@liming links?

[liming]

https://github.com/liming/keystone

[morenoh149]

https://github.com/liming/react-color is the interesting one

[JedWatson]

That's actually not exactly what we need. We haven't made the changes that we need to to go to 2.0.0 yet, so we need a fork of 1.3.8. And it's better if all our deps are loaded from npm, which you can use scoped packages to do.

I've published a fork of react-color to npm that will work for us and am about to update keystone to use it. Should get everything working again, I'm just testing it now. We'll just have to stay with that until @casesandberg gets around to updating react-color again.

[casesandberg]

My bad guys, will get that fixed today 🏇

On Thursday, May 5, 2016, Jed Watson [email protected] wrote:

That's actually not exactly what we need. We haven't made the changes that
we need to to go to 2.0.0 yet, so we need a fork of 1.3.8. And it's better
if all our deps are loaded from npm, which you can use scoped packages to
do.

I've published a fork of react-color to npm that will work for us and am
about to update keystone to use it. Should get everything working again,
I'm just testing it now. We'll just have to stay with that until
@casesandberg https://github.com/casesandberg gets around to updating
react-color again.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/keystonejs/keystone/issues/2601#issuecomment-217184473

[liming]

Good to know!