Getting code actions from ''Vetur', 'Eslint'' takes too long!

[daolanfler]

• I have searched through existing issues
• I have read through docs
• I have read FAQ

Info

• Platform: macOS
• Vetur version:0.26.1
• VS Code version: 1.47.3

Problem

Since I upgraded Vetur from 0.25.0 to 0.26.1, after I edit and save .vue files, vscode get stuck with this promote:

even though the change is very mirror. I have to downgrade to 0.25.0 to avoid this !

local eslint version is eslint@6.8.0
here is my vsocde setting:

{
    "vetur.format.defaultFormatterOptions": {
        "prettier": {
            "semi": false,
            "singleQuote": true,
            "tabWidth": 4
        }
    },
    "vetur.validation.template": true,
    "vetur.format.options.tabSize": 4,
    "vetur.format.defaultFormatter.js": "prettier-eslint",
    "[vue]": {
        "editor.defaultFormatter": "octref.vetur"
    },
    "vetur.format.defaultFormatter.html": "prettier",
    "eslint.alwaysShowStatus": true,
    "eslint.validate": [
        "javascript",
        "javascriptreact",
        "vue",
        "typescript",
        "typescriptreact"
    ],
    "eslint.options": {
        "extensions": [
            ".html",
            ".js",
            ".vue",
            ".jsx"
        ]
    }
}

Reproducible Case

[shiyu3169]

I meet the same issue on Win as well. Downgrading to 0.25.0 temporarily solve problem

[AceYangWQ]

I have the same problem, too

[sethidden]

Not sure if this is not another extension I have but just throwing it out there - does anybody's code sometimes get mangled (eg. one line gets duplicated) after Vetur + Eslint code actions finish after a long time?
eg.
before code actions start to run: props: ['foo']
after code action finish: props:['foo']ops['foo']

[rs3d]

@3nuc This happens for me sometimes, when I cancel the long running action. Maybe eslint/prettier related?

[francoism90]

I'm having the same issue, any solutions/workarounds? :)

Edit: The only thing that works is exiting VSCode and reopen the project. How to provide debug info?

Edit 2: This is on Linux using the latest VSCode.

[octref]

• Does this reproduce when you only have Vetur extension enabled? (Especailly with ESLint disabled)
• Does setting "eslint.codeActionsOnSave.mode": "problems" help?

[sqal]

@octref

Does this reproduce when you only have Vetur extension enabled? (Especailly with ESLint disabled)

For me, yes. When I have both vetur and eslint enabled I am getting the same message as @daolanfler

Saving 'Test.vue': Getting code actions from ''Vetur', 'ESLint'' (configure)

and it hangs for 5 to 7 seconds. Disabling eslint doesn't fix it, Also, one important thing I have to add here is that the mentioned message is shown only once when I try to save .vue file with lint problems. After the message disappears, saving the same file or any other .vue file with lint problems is immediate.

Does setting "eslint.codeActionsOnSave.mode": "problems" help?

Nope.

[borie88]

I've had this issue for quite a long time. I'm using TS in a Quasar project and after a fresh open of VS Code and starting the dev server it works fine for a while. After about a half hour of use, it starts taking a very long time to finish linting lines before save. When saving, if the before-save linting didn't quite finish, I get the code actions pop up for up to half a minute. On a pretty powerful computer, so that shouldn't be the issue

[bbugh]

I'm not sure, but it seems to be related to this issue microsoft/vscode#101555. My hunch is that incomplete save participants are hanging around in a process which ends up slowing everything down. I don't have any way to prove or reproduce, but they both seem to happen around the same time.

[francoism90]

@octref Just to confirm here the setting doesn't fix the 'Getting code actions from..' hang.