dan
Sorry, you shouldn't merge this yet. It seems like removing `NoErrorsPlugin` causes HMR to break if you misspell an `import`. I'll ask around in Webpack repo for some middle solution...
I think my need for `NoErrorsPlugin` was due to React Hot Loader's wrong usage of HMR API, [which I have fixed in 1.3.0](https://github.com/gaearon/react-hot-loader/pull/187). You may want to consider stopping recommending...
Note: you'd need to update RHL to 1.3.0 for this to work
For inspiration, here is the CRA lint config: https://github.com/facebook/create-react-app/blob/next/packages/eslint-config-react-app/index.js
In particular, note that we don't use `ERROR` for anything that is not likely completely broken.
Any person who thinks ordering imports is important probably already has opinions about TSLint config and will configure it themselves anyway. So we might as well relax the default for...
Has this stalled? It’s still kind of brutal. https://mobile.twitter.com/monicalent/status/1043780023730221056
I’m on a vacation. If there’s some problem or question about React please file an issue on React issue tracker.
This also causes warnings like this in dependent libraries with Webpack. One way to fix this would be to refactor env-specific modules to be functions accepting `isClientSide` as an argument....
> if package.json browser is something both respect (even when entering into dependencies) that might be the perfect solution. I can confirm this is the case.