npm@3 warn missing eslint-plugin-react a non react project

[josmardias]

Seems like eslint-plugin-react was moved to peer dependency, and now I'm getting

├── UNMET PEER DEPENDENCY eslint-plugin-react@^4.0.0

I'm using eslint-config-airbnb/base, for a non react project.

How can I get rid of this warning without installing eslint-plugin-react?
Is there any plan for splitting /base to a separate package?

[ljharb]

At the moment, you don't. In order to do that, and not lose the benefit of having it as a peer dep for those using react (like Airbnb), we'd have to make two separate packages "core" and "react", and set up the deps that way.

That would be quite complex - you can just ignore that warning, though?

[josmardias]

I'll have to ignore it...
But it will cost my sanity.

Thanks for the fast reply!

[ljharb]

Given the two options, I'd rather have people in your scenario get the warning rather than people who are using it for react not getting the warning.

I'll leave this open for the time being, because this definitely isn't ideal.

[jguepin]

Same issue here, but the warning prevents my CI service (Codeship) from deploying my application, so I'll have to add the dependency even if not used.

[ljharb]

@jguepin why would you need dev deps (like a linter config) when deploying to production?

[jguepin]

@ljharb you're right, it was the default behavior but I should change that :)

[danactive]

:( I'm also getting this warning too

[tleunen]

@ljharb There's still an issue with it, and it's not just about ignoring the warning...

npm shrinkwrap will fail for any projects without the react plugin.. It doesn't make sense to install the react plugin in a non react project :/

[ljharb]

If we do split the base into a separate package (which is probably the cleanest solution to this problem), I'd likely want to make a scoped package under @airbnb. Is anyone still using npm v1.x (which doesn't support scoped packages) such that this would be a problem?

[josmardias]

I don't believe that anyone is using npm v1.x

[tleunen]

npm v1?! Uh.. Node 0.10 uses npm v2.x, isn't it?

[ljharb]

No, node v0.10 comes with v1.4.29.