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

@commander-api/screen

v0.1.1

Published

ScriptAPI addon template generated by scriptup.

Readme

@capi/screen

ScriptAPI addon template generated by scriptup.

Local library structure

  • package/main.ts: local package source
  • src/main.ts: sample usage that imports from @capi/screen

Setup

npm install

Publish

First publish (manual)

  1. Update name and version in package.json (current import alias: @capi/screen).
  2. Build and publish:
npm run build
npm publish --access public

Subsequent publishes (automated via GitHub Actions)

[!TIP] Using npm Trusted Publishers removes the need to manage NPM_TOKEN in GitHub secrets.

  1. On npmjs.com, open your package → SettingsTrusted Publishers.

  2. Add a trusted publisher:

    • GitHub Actions as the provider
    • Organization or user: Enter your GitHub username or organization name
    • Repository: Enter the repository name where the package is located
    • Workflow filename: publish.yml
    • Environment name: Keep empty
  3. Once configured, delete the NPM_TOKEN secret from GitHub repository settings (not needed anymore).

  4. Bump version in package.json, then create a GitHub release → .github/workflows/publish.yml runs automatically.