Standard show the old error in the parser window when the issue has been fixed

[iwarner]

Please see this attachment

• I changed right quote to a double quote - then back to a single quote - it picked up the error but then persists in showing that there is an error even when fixed

• StandardJS version?
  12.0.1

• VSCode version?
  1.30.1 (1.30.1)

• StandardJS configuration?
  Default setup apart from
  "standard.options": {
  "globals": ["it","test", "expect", "describe"],
  "parser": "babel-eslint"
  },

• What do you have in the OUTPUT panel?
  Nothing

[theoludwig]

Is it still the case with newer versions ? @iwarner

[dziku86]

Is it still the case with newer versions ? @iwarner

Yes it is.

[0xCA]

Windows 10
StandardJS 17
VSCode 1.67.1
Node 16.14.1
Extension 2,1,0

Same issue. After it happens, standard is absolutely stuck. It doesn't detect anything else, auto fix on save is not working. The only way to unstuck it is to hover my mouse over the ghost "issue". After modal about the "error" is displayed, it disappears and standard fully re-activates.
It stucks at false detections most of the time. E.g. half-typed variable in the middle of typing, or trailing spaces after new line, which aren't even there.

[0xCA]

It looks like this, and happens very frequently. It is absolutely unusable. I guess I'm rolling back to Sam Chens 1.4.1 extension and standard 16 (17 is not working with 1.4.1) until this is fixed.