Support pattern in vsce commands

[jdneo]

Now, the vsce command like tool only support to specify the accurate file name to do tasks like publish.

vsce publish -i extension.vsix

I hope pattern match can be supported, like

vsce publish -i *.vsix

[benibenj]

Could you provide a bit more context on why this would be helpful in your case?

[jdneo]

Hi @benibenj,

In CI/CD pipelines, we run several commands towards vsce. Basically package, generate-manifest, publish.

If the command do not specify the output file name, the vsix file name will include the version number, which is dynamic. Things gets a little bit more complicated when it comes to the pre-release.

then it's not easy to specify the input file name for the following action like publish.

Though the problem can be addressed to add -o extension.vsix when packaging, but then I cannot easily see the version number, publisher and extension name from the file name.

[benibenj]

We recommend using -o for these kind of flows.

but then I cannot easily see the version number, publisher and extension name from the file name.

The publisher and extension name should be trivial.

Regarding the version number, why/when do you need it?

• If you already published the extension you can run vsce show EXTENSION_ID to see the latest released versions.
• You can specify the version when you package the extension.
• You can also unzip the .vsix file and read the package.json where you should see the version

[jdneo]

Regarding the version number, why/when do you need it?

Those three solution are not quite fit when it comes to a CICD pipeline. When the pipeline needs to do sth like signing the vsix.

Though I can read the version number before packaging, but that introduces more steps.

[vs-code-engineering]

Hey @benibenj, this issue might need further attention.

@jdneo, you can help us out by closing this issue if the problem no longer exists, or adding more information.