linter not using eslintConfig from package.json

I know in the docs it references using .eslintrc.json to override the linter settings but I’ve tried that as well as my preferred way of having those settings specified in package.json, but it isn’t working.

Here’s the config from package.json:

"eslintConfig": {
    "extends": [
      "eslint:recommended",
      "google"
    ],
    "rules": {
      "no-console": 1,
      "max-len": [
        1,
        100,
        2
      ]
    },
    "parserOptions": {
      "ecmaVersion": 6,
      "ecmaFeatures": {
        "experimentalObjectRestSpread": true
      },
      "sourceType": "module"
    },
    "env": {
      "es6": true,
      "amd": true,
      "node": true
    },
    "overrides": [
      {
        "files": [
          "*test.js"
        ],
        "rules": {
          "no-undef": "off"
        }
      }
    ]
  }

and my devDeps:

"devDependencies": {
    "serverless-plugin-aws-alerts": "^1.4.0",
    "serverless-plugin-ifelse": "^1.0.4",
    "eslint-config-google": "^0.13.0",
    "serverless-bundle": "^1.2.2"
  }

From serverless.yml, I have this under “custom”:

bundle:
    sourcemaps: true
    caching: true
    stats: false
    linting: true

When trying to run sls invoke local for a function, the bundler runs, but then the linter is throwing, despite the rules overrides in eslintConfig:

[jayair]

I tested this a bit more. The caching issue is strictly for ESLint. We could disable the cache and bugs like this won’t happen. https://github.com/AnomalyInnovations/serverless-bundle/blob/master/src/webpack.config.js#L65

Thoughts?

[jayair]

Yeah I see what you mean. It doesn’t happen often but it would be good if we could detect a change and clear the cache somehow.

I’m going to leave this issue open, hopefully somebody can chime in with some ideas.