You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#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.
The text was updated successfully, but these errors were encountered:
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?
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.
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.
#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.
The text was updated successfully, but these errors were encountered: