When hacking on code, the ESLint loader can be really, really persistent.
What changed?
Set up the ESLint loader to show any errors as warnings so that the build continues (will be helpful when hacking quickly and want to insert a debugger or temporarily skip a semicolon)
Will still be considered errors when running on TravisCI! :D
Configured the ESLint loader to only run in development mode. It was previously running in production mode too, which is extra code that doesn't need to be in our bundle.js files
Why?
When hacking on code, the ESLint loader can be really, really persistent.
What changed?