vscode-eslint 0.0.1 → 0.0.3

package/.gemini/agents/vscode-eslint.md

@@ -0,0 +1,23 @@
+---
+name: vscode-eslint-agent
+description: Specialized agent that uses the vscode-eslint LSP server for advanced linting and code analysis.
+kind: local
+# Note: This binary currently speaks LSP. If using as an MCP server, a bridge may be required.
+mcpServers:
+  eslint-lsp:
+    command: "node"
+    args: ["./node_modules/.bin/vscode-eslint", "--stdio"]
+tools:
+  - mcp_eslint-lsp_*
+---
+
+# VSCode ESLint Agent
+
+You are an expert at JavaScript/TypeScript linting using the `vscode-eslint` LSP server.
+Your role is to:
+1. Analyze code for style and correctness issues.
+2. Provide precise fixes for identified problems.
+3. Help the user understand complex ESLint configurations and rules.
+
+You have access to the `vscode-eslint` binary via an MCP-to-LSP bridge (assumed).
+If you cannot communicate with the server, report the error to the user.

package/bin/{vscode-eslint.js → vscode-eslint}

@@ -8,17 +8,18 @@
 'use strict';
 
 const path = require('path');
-const { spawn } = require('child_process');
+const pkg = require('../package.json');
 
 function usage(exitCode = 0) {
 	const msg = [
-		'vscode-eslint (LSP server)',
+		`vscode-eslint (LSP server) v${pkg.version}`,
 		'',
 		'Usage:',
 		'  vscode-eslint --stdio',
 		'',
 		'Options:',
 		'  --stdio     Use stdio transport (LSP over JSON-RPC on stdin/stdout)',
+		'  --version   Show version',
 		'  -h, --help  Show this help',
 	].join('\n');
 	if (exitCode === 0) {
@@ -34,6 +35,11 @@ if (args.includes('-h') || args.includes('--help')) {
 	usage(0);
 }
 
+if (args.includes('--version')) {
+	process.stdout.write(`${pkg.version}\n`);
+	process.exit(0);
+}
+
 const wantsStdio = args.includes('--stdio');
 if (!wantsStdio) {
 	process.stderr.write('error: missing required --stdio\n\n');
@@ -41,16 +47,13 @@ if (!wantsStdio) {
 }
 
 // Run the bundled server produced by server/webpack.config.js
+// We require it directly so it runs in the same process,
+// similar to how typescript-language-server and other LSPs are structured.
 const serverEntry = path.resolve(__dirname, '..', 'server', 'out', 'eslintServer.js');
 
-const child = spawn(process.execPath, [serverEntry], {
-	stdio: 'inherit'
-});
-
-child.on('exit', (code, signal) => {
-	if (signal) {
-		process.exitCode = 1;
-		return;
-	}
-	process.exitCode = code ?? 0;
-});
+try {
+	require(serverEntry);
+} catch (err) {
+	process.stderr.write(`Failed to start ESLint server: ${err.message}\n`);
+	process.exit(1);
+}

package/package.json

@@ -2,7 +2,7 @@
 "name": "vscode-eslint",
 	"displayName": "ESLint",
 	"description": "Integrates ESLint JavaScript into VS Code.",
-"version": "0.0.1",
+"version": "0.0.3",
 	"author": "Microsoft Corporation",
 	"license": "MIT",
 	"repository": {
@@ -13,6 +13,9 @@
 		"url": "https://github.com/shubham151/vscode-eslint/issues"
 	},
 	"publisher": "dbaeumer",
+	"bin": {
+		"vscode-eslint": "bin/vscode-eslint"
+	},
 	"icon": "eslint_icon.png",
 	"categories": [
 		"Programming Languages",