Peer dependencies of eslint-config-react-app should probably be regular dependencies

If user wants only the config and nothing else the one should still install all the deps, which can be done automatically and with no hassle.

Currently, I have to install eslint-plugin-flowtype which I am not even using in my project…

Moreover, version of babel-eslint is outdated (available: 10, listed: 9).

As one of the solutions, maybe, we can create one extra package in this repo and name it like eslint-config-react-app-pack, which will have all the needed deps?

[tlrobinson]

I agree with @kirill-konshin and @skoestler that eslint-config-react-app should mirror the behavior of babel-preset-react-app by including its dependencies as regular dependencies.

I set up a project that mirrors create-react-app’s Babel and ESLint config and about half of the dependencies in my package.json are eslint-config-react-app’s dependencies. It would be nice to trim that down so that one could just add eslint-config-react-app without having to track down all of the dependencies.

[skoestler]

I have a project that is just a component library so I’m not using create-react-app but I wanted the tooling to be consistent with our CRA projects so using babel-preset-react-app and eslint-config-react-app is a great option (I really appreciate that they are published as they are).

I did find it odd that babel-preset-react-app includes all of the plugins as dependencies and eslint-config-react-app uses peer dependencies.

I admit that I could totally be missing the reason for why they are different, but in my case this change would be helpful.