microsoft/vscode-vsce

Publisher required when only packaging an extension

renan-r-santos opened this issue · 5 comments

renan-r-santos commented

#1011 introduced a requirement that we should set a publisher even if we are just calling vsce package and have no intention to publish the artifact.
I wonder if it would be possible to reverse this behavior and allow packaging an extension without defining a publisher.

buildwithzephyr commented

Bump. This requirement was previously removed. #328

benibenj commented

I believe vscode now requires a publisher name when loading an extension from a .vsix file. Is this correct @sandy081? Or do you only validate the publisher if there is one present?

lppedd commented

IMO package should not require a publisher value.
I'd leave that for commands that actually publish, or for the proposed validate command/option, which would ensure the extension is ready to be published.

benibenj commented

You are right. We can allow you to package an extension which does not have a publisher. However, if you have a publisher and it is invalid, we will still throw an error as VS Code won't allow you to load it.

  • 👍1
lppedd commented

Thanks for the fast change!