Closed samestep closed 4 months ago
While I do think most people planning to develop a VS Code extension would already have it installed globally, it doesn't hurt to list it explicitly like this in case they do not.
I suppose, since I often see this in repos for VS Code extensions, but I work on several VS Code extensions and generally prefer not to install npm packages globally.
Anyways, thanks for merging this!
Currently, running
fails if one does not already have
@vscode/vsce
globally installed for some reason. This PR adds it topackage.json
so the above commands work as expected.