Work around ESLint plugin discovery issue

There seems to be no visible progress on https://github.com/eslint/eslint/issues/3458, and since it’s disproportionally affecting our users, maybe we should try doing some hack. The biggest issue is that IDEs can’t discover local ESLint and its plugins because they’re inside node_modules/react-scripts/node_modules.

We could try a few things:

• Ship our own bin script called eslint that launches the “real” eslint with the right NODE_PATH or something (not sure if that would even work)
• Mess with npm internal state and copy all ESLint folders in node_modules one level higher on npm start. This way it won’t work right after installing but should work after the project is first started. Maybe we could even make that a postinstall script for react-scripts.
• Something else crazy.

Regardless of the chosen solution, I’d rather do a hack and fix it up later than keep telling people to install global packages.

[gaearon]

wouldn’t that leave somebody with a hack to deal with once you eject the app?

It should be removed as part of ejecting (we have a way to do that: // @remove-on-eject-begin and // @remove-on-eject-end).

I assume that you are supporting only npm3+ aren’t you?

Nope, we support npm2 because that’s what ships with the stable Node right now.

[gaearon]

¯_(ツ)_/¯ whatever works