npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@bytemain/vsce

v1.96.1

Published

VSCode Extension Manager

Downloads

2

Readme

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.