Summary
The HTML/CSS/ESLint setup instructions recommend installing @zed-industries/vscode-langservers-extracted for the ESLint language server. However, Zed intentionally removed the ESLint server from their fork in zed-industries/vscode-langservers-extracted@d93b048 ("Stop building vscode-eslint").
The @zed-industries/vscode-langservers-extracted@4.10.7 package only ships the vscode-eslint-language-server bin shim (131 bytes) with none of the actual server code — so the ESLint plugin silently fails to start.
Reproduction
npm pack @zed-industries/vscode-langservers-extracted@4.10.7 --dry-run 2>&1 | grep eslint
# Only output: npm notice 131B bin/vscode-eslint-language-server
Compare with the original vscode-langservers-extracted@4.10.0:
npm pack vscode-langservers-extracted@4.10.0 --dry-run 2>&1 | grep -c eslint
# Output: 10 (actual server files)
Suggestion
Update the README and ESLint plugin to recommend the original vscode-langservers-extracted package from hrsh7th, or bundle the ESLint server separately (e.g., directly from vscode-eslint).
Summary
The HTML/CSS/ESLint setup instructions recommend installing
@zed-industries/vscode-langservers-extractedfor the ESLint language server. However, Zed intentionally removed the ESLint server from their fork in zed-industries/vscode-langservers-extracted@d93b048 ("Stop building vscode-eslint").The
@zed-industries/vscode-langservers-extracted@4.10.7package only ships thevscode-eslint-language-serverbin shim (131 bytes) with none of the actual server code — so the ESLint plugin silently fails to start.Reproduction
Compare with the original
vscode-langservers-extracted@4.10.0:Suggestion
Update the README and ESLint plugin to recommend the original
vscode-langservers-extractedpackage from hrsh7th, or bundle the ESLint server separately (e.g., directly from vscode-eslint).