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

vscd

v1.1.0

Published

vscd utility

Downloads

27

Readme

vscd

Visual Studio Code package merger (vscd).

The package.json file is getting rather large for big extensions. This command line tool will search for all contributes.json files in current working directory to build up the package.json.

Each contributes.json file must contain the contributes property. That is the only property that gets looked at.

Arguments

  • --clean (optional, recommended) - the existing package.json contributions will be ignored and will be re-built from the contributes.json files.
  • -d <dir> (optional) - force vscd to use another directory other than your working directory.

Guide

  1. Install vscd as a devDependency: npm i vscd --save-dev
  2. Update your build process to invoke vscd:
"scripts": {
  "package": "vsce package",
  "vscode:prepublish": "rm -rf dist && npm run build",
  "webpack": "vscd --clean && webpack --mode development",
},