I'm also interested in using the ESLint compatibility plugin,
eslint-plugin-compat, which will warn you if you're using JS that is not compatible with the browsers you are targeting (the ESLint plugin also refers to the
So I went ahead and installed and added the plugin to my
.eslintrc.js file, and it seems to be working fine. But when I compile my webpack project, ESLint is pointing out features I'm using in my code, like
Object.values(), that are not compatible with my target browsers. Well yeah, I know that - that's why I'm using Babel, so those features are converted to ones that are compatible for the browsers I'm targeting.
So maybe I'm missing a key point here somewhere. If I'm using Babel already to transpile to compatible code in the browsers I'm targeting, is there still any use for
eslint-plugin-compat in my build process?