You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the latest vscode engine in the generated extension means that the extension (silently) wont' run on any non-latest vscode builds. This can cause a lot of frustration during development, and possibly trying to distribute? Right now it uses v100 which came out 3 days ago, and I'm on 1.99.3, it took me 20 minutes to figure out why my extension just wasn't loading. If it used an older version it would just work for everyone, right?
We want to encourage everyone to use the latest version of VS Code. Also we want to encourage extension authors to use the latest VSCode APIs.
Maybe what should be better is that there's a more prominent warning when you try to launch a non compatible extension. That would encourage you to update VS Code (or reduce the engine version).
Activity
RedCMD commentedon May 12, 2025
you're supposed to set the version to the lowest version you support
setting it to v100 means your extension breaks with v1.99.3
msfeldstein commentedon May 12, 2025
Right, thats why it should generate with a lower version, so it just works for people instead of silently failing
ars-celare commentedon Aug 10, 2025
So, I've started using this tool, and now I read that my extension won't work for a large portion of users unless I change something.
Can you please document that?
What do I have to change to get the extension to work on more machines?
Is there really no way to do this during generation?
aeschli commentedon Dec 2, 2025
We want to encourage everyone to use the latest version of VS Code. Also we want to encourage extension authors to use the latest VSCode APIs.
Maybe what should be better is that there's a more prominent warning when you try to launch a non compatible extension. That would encourage you to update VS Code (or reduce the engine version).