Skip to content

parse extension package name in case of dependent extension#6680

Draft
davidbrai wants to merge 1 commit into
mainfrom
fix/extension-label-of-sibling-extension
Draft

parse extension package name in case of dependent extension#6680
davidbrai wants to merge 1 commit into
mainfrom
fix/extension-label-of-sibling-extension

Conversation

@davidbrai

@davidbrai davidbrai commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

partially fixes: #6619

@xl0

xl0 commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Do you really want to support dependent extensions? Which is different from extensions depending on an npm package that is shared between a group of extensions.

@davidbrai

Copy link
Copy Markdown
Contributor Author

@xl0 not sure yet. in practice we support it right now as shown here: #6619
do you have an idea of how we should handle these cases?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

On windows dependent extensions pulled in by an npm package mislabeled and show absolute path in banner

2 participants