Vscode-vsce: Publish error : ERROR Missing publisher name.

[RufusWein]

Well, Yesterday I did my first extension and today when I going to publish it doesn't work.

vsce create-publisher rufuswein
[OK]

vsce login rufuswein
[OK]

vsce ls-publishers
rufuswein [OK]

vsce publish
ERROR Missing publisher name. Learn more: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#publishing-extensions [WTF!]

vsce package
ERROR Missing publisher name. Learn more: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#publishing-extensions [WTF!]

vsce -V
1.64.0[OK]

node --version
v10.16.0[OK]

npm --version
6.9.0[OK]

git --version
git version 2.21.0.windows.1

All post about a like issue it has not helped me to solve this.
https://github.com/Microsoft/vscode-vsce/issues/110
https://github.com/Microsoft/vscode-vsce/issues/86

My Git repositorie:
https://github.com/RufusWein/saveall

[joaomoreno]

From https://code.visualstudio.com/api/working-with-extensions/publishing-extension#create-a-publisher

A publisher is an identity who can publish extensions to the Visual Studio Code Marketplace. Every extension needs to include a publisher name in its package.json file.

Eg:

    "publisher": "rufuswein"

[RufusWein]

Ok João is that, thank you very much.

[tweakimp]

@joaomoreno It would be better if the error message told us WHERE it is missing.

[rogersanbr]

Also, the yeoman vscode ext generator could bring this by default

[ORESoftware]

this error is not good. it should say:

missing "publisher" field in package.json

very dumb error message

[jfthuong]

Also, the yeoman vscode ext generator could bring this by default

I have created an issue for yeoman generator: https://github.com/microsoft/vscode-generator-code/issues/200

[aeschli]

Maybe vsce can prompt for a publisher (or suggest the logged-in user) and update package.json?

We removed the What your publisher prompt from yo code as it confused a lot of new users. It's better to start worry about the publisher once you are ready to publish.

[HansUXdev]

I published an extension in the past and didn't need this. I don't get why any coder or company would introduce a breaking change and not update the docs especially a big company like Microsoft...

[augwu-thortech]

The issue seems to be that a user gets orphaned when they hit this step. The page which is link makes the solution non-obvious, is buried in the page, and links to an even more generic doc.