The @vscode/vsce package is bloated (~75 MB with dependencies...average Microslop TS project). vsxtools has it as an optional dependency, required for packing and publishing extensions. Creating our own vsce alternative can:
- Decrease bloat in vsxtools installs
- Speed up installation of tools to pack extensions
- Reduce the supply chain attack surface by removing dependencies
- Offer an alternative tool for packing extensions
- Add more functionality to vsxtools
- Introduce APIs for VSCode extension packing
Implementation
Out of all vsce commands, we currently plan to implement the following:
We have no plans to reimplement the proprietary parts of vsce, such as publish.
We want extra feedback on reimplementing the show and search commands.
Goals
The
@vscode/vscepackage is bloated (~75 MB with dependencies...average Microslop TS project). vsxtools has it as an optional dependency, required for packing and publishing extensions. Creating our own vsce alternative can:Implementation
Out of all vsce commands, we currently plan to implement the following:
packlsWe have no plans to reimplement the proprietary parts of vsce, such as
publish.Goals