"0:0 error Module Error [...]" when using with webpack

Hello,

Using this in my package.json file :

    [...],
    "babel-eslint": "^9.0.0",
    "eslint": "^4.16.0",
    "eslint-config-airbnb": "^17.1.0",
    "eslint-loader": "^2.1.0",
    "eslint-plugin-import": "^2.8.0",
    "webpack": "^4.17.1",
    [...]

and this in my .eslintrc:

{
    "parser": "babel-eslint",
    "rules": {
        [...]
    }, 
    "globals": {
        [...]
    }
    "extends": "airbnb-base"

It seems there is a bug when using webpack --mode development (even in production mode). It returns me this:

./assets/javascripts/forum.es6
  0:0  error  Module Error (from ./node_modules/eslint-loader/index.js):

./assets/javascripts/global.es6
  0:0  error  Module Error (from ./node_modules/eslint-loader/index.js):

✖ 2 problems (2 errors, 0 warnings)


npm ERR! Linux 4.15.17-1-pve
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "dev"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! humanoid-redesign@3.0.0 dev: `webpack --mode development`
npm ERR! Exit status 1

It’s not a problem with my es6 files: if I remove their content, the problem is still there.

If I remove the airbnb-base line in my .eslintrc config file, everything works fine.

Maybe it can be a problem with Eslint directly, but i’m really not sure after trying to remove airbnb-base in my .eslintrc file.

Thanks for any help with this.

[jaythomas]

your entire website stops working when you have a linting error

This is entirely dependent on the development ecosystem. In the case here of webpack + eslint-loader it won’t stop the build but instead provide an error log message to the output or reporter.

[ljharb]

@jaythomas what’s “wrong” is that your entire website stops working when you have a linting error, which introduces unnecessary friction, and encourages linting less so that it obstructs your build less - when in fact, you should be linting as much as possible.

You’re right about the order of the config keys 😃