vscode-eslint: Eslint is not linting on save (with new setting in json)

We have been using eslint heavily, but with the new update(2.0.4) our files are no longer being linted.

My output dialog box keeps saying Cannot find module 'babel-eslint' and Cannot find module 'eslint-config-airbnb' if I attempt to use the default formatter.

Is there a new way to tell eslint to use my current directory? I have all of my node modules installed and set up, I have uninstalled and reinstalled, removed yarn.lock, etc.

I have also updated my vscode settings.json to use the

"editor.codeActionsOnSave": {
        "source.fixAll": true,
        "source.fixAll.eslint": true,
},

Any help would be siiiiiiiiick.

Edit: we are using an .eslintrc.js file.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 3
  • Comments: 19 (6 by maintainers)

Most upvoted comments

As a quick fix, you can use an older version (1.9.1) by clicking the gear icon beside ESLint on VSCode extensions.

Meanwhile, I made a video demonstrating the auto fix on save issue https://github.com/microsoft/vscode-eslint/issues/841#issuecomment-566814419 Is this the same problem you’re having or a different one?

Screenshot_260

Issue fixed with 2.0.11

Confirm having this issue, tried toggling all auto save toggles available