VSCode扩展本地开发正常，安装后报错：command 'extension.goToTest'未找到

Hey there! Let's tackle this "command not found" issue you're hitting with your Rails test file extension—super common when moving from local dev to a packaged extension, so let's break down the fixes step by step:

First off, make sure your command ID is perfectly matched everywhere. The contributes.commands section in package.json needs to explicitly declare extension.goToTest, like this:

"contributes": {
  "commands": [
    {
      "command": "extension.goToTest",
      "title": "Go to Test File"
    }
  ]
}

Also confirm that in your extension's entry file (usually extension.js/extension.ts), you're registering the command with the exact same ID:

vscode.commands.registerCommand('extension.goToTest', () => {
  // Your command logic here
});

Even a tiny typo (like extensions.goToTest instead of extension.goToTest) will break this in the packaged version, but might slip through local testing.

Since you suspect dependency issues, verify that all packages your extension needs to run are listed under dependencies (not just devDependencies) in package.json. Dev dependencies are excluded from the packaged extension, so any runtime reliance needs to live in the dependencies block:

"dependencies": {
  // Add any packages your extension uses at runtime here
  "ruby-parser": "^1.0.0"
},
"devDependencies": {
  // Keep development-only tools here (like TypeScript, VS Code types)
  "@types/vscode": "^1.80.0",
  "typescript": "^5.1.6"
}

Local testing (F5) activates your extension immediately, so you might not notice missing activation events until packaging. Make sure package.json includes an activation trigger for your command:

"activationEvents": [
  "onCommand:extension.goToTest",
  // Optional: Add a trigger for when a Rails project is detected
  "workspaceContains:**/config/routes.rb"
]

Without this, VS Code won't load your extension when the command is called, leading to the "command not found" error.

Sometimes dependencies or files don't bundle correctly. Unzip your generated .vsix file and check:

• Does the node_modules folder include all your dependencies packages?
• Are all your extension's source files (like your command implementation) present?
• Are there any build artifacts missing that your extension relies on?
  You can also run vsce package --debug to get warnings about missing files or dependency issues during packaging.

Local VS Code caches or existing extensions might interfere with testing. Try installing your .vsix in a fresh temporary instance:

code --user-data-dir ./temp-vscode-env

If the command works here, the issue was likely local caching or conflicting extensions in your regular setup.

内容的提问来源于stack exchange，提问作者Szymon Borucki