Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command 'eslint...' not found since updating to 2.4.4 #1777

Open
the21st opened this issue Jan 23, 2024 · 9 comments
Open

Command 'eslint...' not found since updating to 2.4.4 #1777

the21st opened this issue Jan 23, 2024 · 9 comments
Labels
info-needed Issue requires more information from poster

Comments

@the21st
Copy link

the21st commented Jan 23, 2024

Since I upgraded to 2.4.4, I am getting this error when I try to invoke any eslint command from the command palette:

Vscode version: 1.81.1

image

Downgrading the plugin to 2.4.2 seems to resolve the problem.

@RussOakham-BG
Copy link

Had the same when trying to restart my ESLint server locally, as linting was no longer showing in-document on VSCode (No red squiggles).

Would get command eslint.restart not found error upon trying.

Rolling back to the prior version resolved it for me in the short term.

@dbaeumer dbaeumer added the info-needed Issue requires more information from poster label Jan 23, 2024
@dbaeumer
Copy link
Member

Anything in the ESLint output channel ?

@6feferonka9
Copy link

I second this, latest version is broken. No command works.

Only output is: The language client requires VS Code version ^1.82.0 but received version 1.80.0

After updating VS code it seems to be working

@yisibell
Copy link

I got Same problem in 2.4.4, so that i have to use 2.4.2. And there is nothing in output channel.

@dbaeumer
Copy link
Member

@yisibell which version of VS Code are you using?

@yisibell
Copy link

yisibell commented Jan 24, 2024

@dbaeumer vscode 1.73.1

ff9707557768478d5424300b68833f6

@the21st
Copy link
Author

the21st commented Jan 24, 2024

@yisibell which version of VS Code are you using?

I was on vscode 1.81.1. After updating to 1.85.2, the issue seems to be resolved 🎉

@dbaeumer
Copy link
Member

Yes, version 2.4.4 of the extension requires at least 1.82.0 of VS Code. I made a change to the Extension that will avoid that the extension gets installed in the future when the minimum VS Code version is not available. I the meantime all I can recommend to either upgrade to 1.82.0 of VS Code or to downgrade the extension to 2.4.2.

@michael-chan-mox
Copy link

Yes, version 2.4.4 of the extension requires at least 1.82.0 of VS Code. I made a change to the Extension that will avoid that the extension gets installed in the future when the minimum VS Code version is not available. I the meantime all I can recommend to either upgrade to 1.82.0 of VS Code or to downgrade the extension to 2.4.2.

Same here, upgrading VsCode works!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

6 participants