Repository navigation
Create a nightly/insiders extension in the Marketplace #17196
Description
Activity
microsoft/vscode#15756 may lead to this being put on hold.
A wrench in this plan is that Pylance hard depends on the core extension, as it's not the one running the server and such; if there are two Python extensions, we'd necessarily have to drop our side of the dependency and then figure out what to do with people who discover and install the stack via the Pylance extension.
Reacted by Brett CannonJake Bailey (@jakebailey) chances are we will probably go with the solution the VS Code core team is proposing and using the mechanism where there's just the single extension and VS Code controls which VSIX to download, but good point about how this might make it messy unless you also publish an insiders extension that relies on our insiders extension.
Closing in favour of #18144
- locked as resolved and limited conversation to collaborators
on Jan 9, 2022
This would replace our bespoke insiders channel download/install mechanism so we can rely on VS Code to update.
package.prod.jsonwhich contains only that which would differ from the nightly build#17133