Don't crash if users mistakingly install babel, webpack, jest, loaders, etc, at the top level

[gaearon]

I’ve seen this issue multiple times. For some reason people don’t believe react-scripts is enough and try to install Babel, Webpack, and friends themselves. This can break things.

We need to mitigate this somehow.

[gaearon]

@anyayunli If you’d like control over configs, run npm run eject and you have it. This issue is not related to that.

[langpavel]

This is about inexperienced developers. It can be limited only by more educational examples and strict rules for opening issues.

[langpavel]

And more visible dedicated site for users, stack overflow is not enough

[Timer]

Is there anything wrong with us showing a nasty-looking warning when people do this?

[langpavel]

No, really not. You are experiencing success, you only need way to fastly redirect people from Github to more general discussion about when they should eject!

[Timer]

Optimally, we want people not to eject. I feel like there's way too many small things people eject for that's accomplishable without ejecting (e.g. using sass-loader).

[langpavel]

So, this can be statistically observed. You can inject some questionary into eject command with helpful links. This is task for @cpojer like person:-)

[Timer]

@gaearon what about something like this?

[langpavel]

Nice, but not enough. It will works BUT you are not providing hint. When you run eject, it should ask you why you need eject providing most relevant information. No way back after. That's ok, but warn about they are not supported by this awesome toolkit any more..

[gaearon]

I’d like us to first look into why this breaks CRA. If there's a version conflict, react-scripts should use its own version of webpack. We should fix whatever breaks so that outer version of webpack is just ignored. We can optionally warn on top of that but first we should fix the breakage.

[langpavel]

Different idea. Can you hook yarn with CRA? For example as preinstall, pre-add in package.json. I know, this is something new! But this is in your possibilities!
Or you can create recommended way to install new dependencies with CRA specific cli tool, promote it and drive mainstream. This will give you less observable force than patching yarn. Controversial but, hey, look at real people!

[gaearon]

We already use Yarn when it’s installed. It doesn’t solve the problem though.

[langpavel]

Yarn hook which will dog watching what you want add

[langpavel]

It's entire new space not possible today. Yes you can give recommendations only..:
You just installed package xyz. Did you consider this way? Http....