2015-11-19 11:17:47 +01:00
# vsce
2019-09-22 16:11:17 +05:30
2015-11-19 11:17:47 +01:00
> *The Visual Studio Code Extension Manager*
2019-06-20 11:29:57 +02:00
[![Build Status ](https://dev.azure.com/vscode/VSCE/_apis/build/status/VSCE?branchName=master )](https://dev.azure.com/vscode/VSCE/_build/latest?definitionId=16& branchName=master) [![npm version ](https://badge.fury.io/js/vsce.svg )](https://badge.fury.io/js/vsce)
2015-11-19 11:17:47 +01:00
2019-06-20 11:23:47 +02:00
## Requirements
2015-12-03 09:36:10 +01:00
2018-03-19 10:16:54 +01:00
- [Node.js ](https://nodejs.org/en/ ) at least `8.x.x`
2015-12-03 09:36:10 +01:00
2020-01-13 11:56:24 +01:00
## Usage
`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 ](https://github.com/microsoft/vscode-vsce/blob/master/src/api.ts ).
2020-07-25 15:10:44 -07:00
> **Warning:** When using vsce as a library be sure to sanitize any user input used in API calls, as a security measure.
2020-01-13 11:56:24 +01:00
2019-06-20 11:23:47 +02:00
## Development
First clone this repository, then:
```sh
yarn
yarn watch # or `watch-test` to also run tests
```
Once the watcher is up and running, you can run out of sources with:
```sh
yarn vsce
```
### Publish to NPM
Simply push a new tag and the CI will automatically publish to NPM. The usual flow is:
```sh
npm version [minor|patch]
git push --follow-tags
```
## About
2015-09-28 19:34:49 +02:00
2018-12-16 20:50:29 -08:00
This tool assists in packaging and publishing Visual Studio Code extensions.
2015-10-09 10:19:23 +02:00
2018-12-16 20:50:29 -08:00
Read the [**Documentation** ](https://code.visualstudio.com/api/working-with-extensions/publishing-extension ) on the VS Code website.