VS Code Extension Manager https://github.com/microsoft/vscode-vsce

Find a file

JeffreyCA 16f35b3485 Add githubBranch flag to control the branch for GitHub relative links		2020-08-08 22:33:50 -04:00
.vscode	Update launch.json to be useful for extension debugging	2020-06-26 17:43:19 +02:00
resources	Add property for supported languages	2018-09-14 11:56:45 -07:00
src	Add githubBranch flag to control the branch for GitHub relative links	2020-08-08 22:33:50 -04:00
.gitignore	remove package-lock.json	2019-01-17 08:37:20 +01:00
.npmignore	fix types	2019-04-12 16:42:09 +02:00
azure-pipelines.yml	improve node and yarn versions	2019-06-20 11:23:41 +02:00
LICENSE	Update LICENSE	2015-11-18 15:16:54 +01:00
package.json	Fix issues with missing out directory	2020-06-26 14:36:59 +02:00
README.md	Fix typo in README	2020-07-25 15:10:44 -07:00
ThirdPartyNotices.txt	add ThirdPartyNotices.txt	2015-12-16 18:27:13 +00:00
tsconfig.json	ts: noUnusedLocals, noUnusedParameters	2019-11-28 16:50:49 +01:00
yarn.lock	Bump lodash from 4.17.15 to 4.17.19	2020-07-16 22:33:45 +00:00

vsce

The Visual Studio Code Extension Manager

Requirements

vsce is meant to be mainly used as a command line tool. It can also be used a library since it exposes a small API.

Warning: When using vsce as a library be sure to sanitize any user input used in API calls, as a security measure.

First clone this repository, then:

yarn
yarn watch # or `watch-test` to also run tests

Once the watcher is up and running, you can run out of sources with:

yarn vsce

Simply push a new tag and the CI will automatically publish to NPM. The usual flow is:

npm version [minor|patch]
git push --follow-tags

This tool assists in packaging and publishing Visual Studio Code extensions.

Read the Documentation on the VS Code website.