Connor Peet

You could set `"nodejs-testing.extensions": []` in the folder you want to disable it in (in `.vscode/settings.json` within that folder)

There's no such option. One option is to use the node launch type which avoids using a terminal and should be overall faster ```js { "name": "Next.js: debug full stack",...

I had a request on this for VS Code. I didn't dive deep into it but there are a couple scenarios that complicate this. 1. Servers that provide a dynamic...

Yes. It's a bit of a pain because, given both (2) and (3) happen it's a `NxM` multiplier to the number of tools, but it's possible.

(though practically only a relatively small number of servers will get localized into a large number of languages)

I think tool representation overall, either in the registry spec or MCP metadata, would be useful. Currently clients need to start servers in order to know what tools, prompts, etc....

This is an API I'm working on to have a VS Code extension version of the server manifest with static Tools declarations, to serve as possible inspiration: https://github.com/microsoft/vscode/issues/272000

The C# extension is the place to file this. This is the repo for VS Code itself. Thanks!

Modern versions of test-electron include a helper you can use, e.g. ``` await runVSCodeCommand(['--install-extension', 'ms-python.python']); ```

Are you running with coverage? This was a bug in Node.js: https://github.com/nodejs/node/issues/46110