Vscode-vsce: Support for scoped naming, e.g., @myscope/package-name?

[vazexqi]

I have an VS Code extension that I would like to scope to my org. In usual NPM, I would set name: @myscope/package-name in package.json.

However, when I use that with vsce, it says

vsce package
Error: Invalid extension name '@myscope/package-name

I think this is because of the regex check at https://github.com/Microsoft/vscode-vsce/blob/master/src/validation.ts#L3

Are there plans to support scoped names for extensions?

[joaomoreno]

There is no upcoming support for scopes. We don't store extensions in NPM, but in the VS Marketplace.

[drochgenius]

I find it a bit confusing the vscode extensions use the package.json as their manifest, since this is the NPM package manifest file.

If vscode extensions are meant to be published only to the vscode markeplace, they could have their own manifest for publishing to that marketplace, with a different name, e.g. vscode-manifest.json.

This way it would not conflict with package.json conventions.

[eightHundreds]

vscode-private-extension-manager suport store extensions in NPM

[madcapnmckay]

+1 for scoped extension packages.

If trying to use a private extension registry scoped naming is preferable.