I'm new to working on VS Code extensions. I have my first extension working in JavaScript and published it to the Marketplace. Now I want to work on improving it.

But when I test it with F5 is the version I'm trying to test guaranteed to override the installed one?

And if I disable the installed one, does it do it in such a way that both the installed one and the one I'm working are both detected as disabled?

Is it better then just to uninstall while I'm working on it?

In short, what's the way to make sure there's no clash between your old version and testing version when working on your own VS Code extension in VS Code?

Google surprisingly doesn't find previous discussion of this for me. I have also tried adding a vscode.window.showInformationMessage and a console.log in various parts of the code but I don't see them. Not in the "output" or the "debug console" or either the editor I'm working in, or the one spawned for testing.

I'm actually trying to convert the extension from .js to .ts and I've tried F5 with the compiled .js or the .ts source in the editor. It seems to make no difference.

I'm new to working on VS Code extensions. I have my first extension working in JavaScript and published it to the Marketplace. Now I want to work on improving it.

But when I test it with F5 is the version I'm trying to test guaranteed to override the installed one?

And if I disable the installed one, does it do it in such a way that both the installed one and the one I'm working are both detected as disabled?

Is it better then just to uninstall while I'm working on it?

In short, what's the way to make sure there's no clash between your old version and testing version when working on your own VS Code extension in VS Code?

Google surprisingly doesn't find previous discussion of this for me. I have also tried adding a vscode.window.showInformationMessage and a console.log in various parts of the code but I don't see them. Not in the "output" or the "debug console" or either the editor I'm working in, or the one spawned for testing.

I'm actually trying to convert the extension from .js to .ts and I've tried F5 with the compiled .js or the .ts source in the editor. It seems to make no difference.

• vscode-extensions

1 Answer 1

There's no generic answer to your question, since there can be many reasons why multiple versions could clash (e.g. when they use the same files or databases), but in general there's no problem developing your new version, while the old one is installed, because VS Code opens a development host with your new version when you start debugging.