-
Notifications
You must be signed in to change notification settings - Fork 29.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension installation dependencies #11937
Comments
As discussed with @egamma, we're going with an approach in which 100% of this work in on our side. An extension can list other extensions it wants to be installed in the user's machine, when installing itself. As a consequence, this connection won't surface in the Marketplace, only at extension installation time, within VS Code itself. Any other approach would require cooperation with the Marketplace to create a first class concept of extension dependencies or packs. |
Will this be done in the manifest file or where will it be done? I am not opposed to the approach, but I can see some benefit to having dependent extensions surface in the Marketplace's UI. |
We decided to use the (already existing) Going with this decision won't luck us down and will let the Marketplace reflect that data in their UI, if we want to go that way in the future. |
Cool sounds good to me. |
We want to support extensions depending on other extensions and having that transitive closure installed when installing the first one. Eg.
vscode-go
could depend onvscode-go-syntax
.This requires
vsce
work:package.json
to indicate extension dependencies:extensionDependencies
Microsoft.VisualStudio.Code.ExtensionDependencies
For
vscode
:Install all
,Install this extension only
,Cancel
)We're leaving Uninstall out of the story for now.
The text was updated successfully, but these errors were encountered: