Eslint question about react-webpack-boilerplate HOT 5 CLOSED

This is actually a pretty nice idea, @Piero87. I've played a bit with the loader and it seems to be working great with webpack 3.

Something I've been thinking is, should I keep the eslint rules as it is, using Airbnb's config, or rework them to return warnings instead of errors (similar to create-react-app). What do you thing?

Regardless of that, I would most certainly integrate eslint-loader to the project. I will first test it a bit more on a branch, react-webpack-boilerplate/eslint-loader, and I hope to add it to the project by the end of the week.

Once again, thanks for the great suggestion! 🎉

from react-webpack-boilerplate.

I appreciate you think is a good idea, I think that to write a good JavaScript You have to stick to the guides, otherwise you risk only with the warnings of not looking and writing maybe in a bad way. If you work in a team for example is really important that everyone write the same code As if everyone was the same person, giving continuity to the code. So the Eslint give you a block with error that you must to fix before go on. I take that suggestion reading this amazing blog:
https://www.robinwieruch.de/react-eslint-webpack-babel/#eslintBabel
https://www.robinwieruch.de/minimal-react-webpack-babel-setup/#babelSetup

from react-webpack-boilerplate.

From what I understand you favor eslint's errors more than the warnings, right?

from react-webpack-boilerplate.

Yes, I'm always in favor of writing a good javascript, so I in this way is better the error than the warning. I don't know if it's possible in webpack, but you could use a parameter to enable or disable it at the startup of the script, maybe with two start different start script.

from react-webpack-boilerplate.

With #148, the project now supports continuous linting.

from react-webpack-boilerplate.