Code-server: Unable to install ESLint extension because it is not compatible with the current version of VS Code

[talentlessguy]

• code-server version: 1.39.2
• OS Version: Manjaro Linux 5.4
  

  Description

When I try to install ESLint extension, I get this:

Steps to Reproduce

1. Install code-server from AUR (yay -S code-server)
2. Search for ESLint
3. Hit "Install"

Related: #43

[Bessonov]

Should it be fixed by https://github.com/cdr/code-server/issues/1220?

[talentlessguy]

Should it be fixed by #1220

Yes, it should but it is not merged yet

[mwswindle]

FYI, theres a work around, building the latest supported version straight from the git repo.

cd
git clone https://github.com/microsoft/vscode-eslint.git
cd vscode-eslint
git checkout tags/release/1.9.1
npm i
npx vsce package

Next, click on the Extensions tab, and in the 3-dot-menu drawer, first click Disable Auto Updating Extensions.
Then, click on Install from VSIX in the 3-dot-menu drawer, navigate to the git folder, and select the vsix.

You can delete the git folder now.

[hasip-timurtas]

download this to your server:
https://dbaeumer.gallery.vsassets.io/_apis/public/gallery/publisher/dbaeumer/extension/vscode-eslint/1.9.0/assetbyname/Microsoft.VisualStudio.Services.VSIXPackage

and
CTRL+SHIFT+P
and type VSIX
then find the file you downloaded from the link above.
Now you installed an older version of ESlint that can work with your vscode.

[cstrat]

Thanks @hasip-timurtas - I wasn't able to get it to work by doing what @mwswindle suggested, but downloading the binary direct has worked so far.

[sr229]

We updated to 1.4x so this should be fixed now

[cstrat]

I updated to the latest release docker yesterday and it didn't work?
Is docker updated with 1.4x?

edit: sorry I checked and I am on 1.39 😅

[code-asher]

The latest and v2 tags haven't been updated yet. There is a 2.1698 tag
but I'll go ahead and update latest and v2 now. I'll need to make sure
they get updated after we've verified it works in the future.

[cstrat]

Yeah my mistake. My experience with docker is limited largely to this project only so I didn’t realise latest wasn’t automatically the latest.

Thanks for all the good work on the project!

[code-asher]

Nah, it's definitely my bad for having a release and yet not updating
the latest tag. Shouldn't happen again. Thanks for the kind words!

[code-asher]

Oof, this is embarrassing. I didn't check the output of my push
yesterday and it didn't actually work. I did it just now so latest is
now actually latest.