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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@joepham/vsm

v0.1.9

Published

VS Code Shortcut Manager CLI

Readme

@joepham/vsm

VS Code Shortcut Manager CLI, re-homed into this repository as the new source of truth.

Installation

Recommended (global CLI install):

npm i -g @joepham/vsm
vsm --version

Update global install:

npm i -g @joepham/vsm@latest

Current Status

  • Phase A bootstrap completed.
  • Non-interactive command core implemented for all primary commands.
  • Interactive fallback prompts are enabled for create, adopt, inspect, update, remove when required inputs are missing.
  • Canonical command model is vsm <command>.
  • Changesets and publish workflow scaffolding are added for release preparation.
  • CI verification runs build + parity smoke + negative smoke checks.

Command Model

Canonical commands:

  • vsm list
  • vsm create
  • vsm adopt
  • vsm inspect
  • vsm update
  • vsm remove
  • vsm doctor

Bundle ID Behavior (macOS)

  • --bundle-id controls the shortcut .app identity and conflict detection.
  • macOS window grouping still follows the running target-app process (for example Visual Studio Code.app).
  • If you need separate Dock/window identity, use different target app bundles (for example separate copies of VS Code app).

UI Differentiation Metadata

vsm can write per-shortcut UI metadata into the shortcut config and apply it to the shortcut's User/settings.json.

  • --window-label: label stored in metadata and used to auto-build a default title when --window-title is not provided.
  • --window-title: explicit VS Code window.title template.
  • --window-accent: single accent color (#RGB or #RRGGBB) for all modes (legacy/simple mode).
  • --window-accent-dark: accent color for dark themes.
  • --window-accent-light: accent color for light themes.

Example:

vsm update --name "Visual Studio Code Joe 1" \
	--window-label "JOE 1" \
	--window-title '[JOE 1] ${rootName}' \
	--window-accent-dark "#4B5563" \
	--window-accent-light "#9CA3AF"

This provides a second differentiation mechanism beyond app identity: title and color cues that adapt between dark and light themes.

Development

npm install
npm run build
node ./bin/run.js --help
npm run smoke:parity
npm run smoke:negative

Migration Policy

  • Migration and deprecation timeline: docs/MIGRATION.md