yarn start returns different eslint results than eslint src

[mihok]

I found this after working on #21 PR. There are different results spit out when running yarn start to what spits out running eslint src

Some errors are not reported with yarn start and then people may forget to run eslint src separately, finally getting a surprise when they make a PR

[tazsingh]

We should use the eslint-loader in Webpack to report these ESLint errors via Webpack as well.

[alex-wilmer]

let's see if we can make that work without ejecting the webpack config first. I can look into it

[kieran]

not applicable anymore