Skip to content

sebas2day/vscode-vsce

 
 

Repository files navigation

vsce

The Visual Studio Code Extension Manager

Build Status npm version

Requirements

Or simply Docker.

Usage

Install vsce globally:

npm install -g vsce

Verify the installation:

vsce --version

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. When using vsce as a library be sure to sanitize any user input used in API calls, as a security measurement.

Usage via Docker

You can also build a container for running vsce:

git clone https://github.com/microsoft/vscode-vsce
cd vscode-vsce
docker build -t vsce .

Validate the container:

docker run -it vsce --version

Publish your local extension:

docker run -it -v $(pwd):/workspace vsce publish

Development

First clone this repository, then:

npm i
npm run watch # or `watch-test` to also run tests

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

npm run vsce

Publish to NPM

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

About

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

Read the Documentation on the VS Code website.

About

VS Code Extension Manager

Resources

License

Security policy

Stars

Watchers

Forks

Packages

No packages published

Languages

  • TypeScript 99.9%
  • Other 0.1%