vsce package should not check for publisher

[octref]

Repro:

• Clone a sample from https://github.com/Microsoft/vscode-extension-samples
• Run vsce package
• vsce should not check for publisher for generating the VSIX

[bkelley13]

For extension packs, too.

[bsed]

For extension packs, too.

[Supitto]

You can solve this by adding a 'publisher' field in package.json, vsce will generate the package with no problems

[SimoneRichetti]

I agree with the issue too. If I use a private npm repository to share my extension only with my colleagues I don't want to create an Azure organization. This check should be done when I publish to the public marketplace, not when I generate the vsix package.

[SimoneRichetti]

Hi @sergeiudris, I had that error for two reasons:

1. My publisher name was not correct: only letters, numbers and hyphens are allowed;
2. I put local images in the README of the extension, which is not allowed, you can only put https links.

Maybe these tips are helpful. I link you the issue that I opened on another repo but correlated to this problem: joelspadin-garmin/vscode-private-extension-manager#40 (comment)

[SimoneRichetti]

You are welcome!
I think that a lot of people are falling into this error. Maybe a mention of that should be added to the documentation? I mention @joaomoreno as the assignee of the issue.

[github-actions]

🎉 This issue has been resolved in version 2.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀