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

Find a file

João Moreno 3dc84fbd22 Merge pull request #437 from jamesgeorge007:update-dep Fixed markdown-it security vulnerability		2020-04-02 09:48:12 +02:00
.vscode	setup default build task	2020-02-18 09:59:58 +01:00
resources	Add property for supported languages	2018-09-14 11:56:45 -07:00
src	Change a console.warn to console.log for an informational message	2020-03-31 08:29:57 -07:00
test	mocha opts	2016-09-22 16:30:50 +02: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	chore: update markdown-it	2020-04-01 12:01:50 +05:30
README.md	Update README.md	2020-01-13 11:56:24 +01: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	chore: update lock file	2020-04-01 12:03:31 +05:30

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 measurement.

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.