@vscode/vsce exposes an API for publishing, with configurable options also exposed.

Given this, it would be possible to have a flow where:

1. vsce-pnpm handles packaging extensions using pnpm
2. vsce is called to handle publishing
3. the entire chain is effectively handled by vsce-pnpm, marking simplicity

One thing that needs to be noted is that if a .vsix is not specified, vsce will auto-build and publish it, I think without ever outputting the built file, which wouldn't be possible this way, however I think that it's not really that big of an issue and the script can always clean it up after if that's the desired behaviour.

exciting package, can't wait to use it!