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

@sigx/cli

v0.10.0

Published

Unified CLI for SignalX — create, dev, build, and run projects

Readme

@sigx/cli

The unified sigx command-line tool — daily-driver CLI for SignalX projects (web and Lynx).

npm i -D @sigx/cli
# then:
npx sigx <command>

After scaffolding with npm create @sigx@latest, the generated project depends on @sigx/cli directly. The sigx binary is the single entry point for everything: scaffolding, dev servers, builds, previews, and platform-specific commands provided by plugins. Any package can extend sigx with new commands via a sigx-cli.plugin field in its package.json.

📚 Documentation

Full command reference, headless create flags, the plugin API and live examples → https://sigx.dev/cli/

sigx create my-app    # scaffold a project (interactive)
sigx dev              # start the dev server
sigx build            # production build

Run sigx --help for the full live list (varies by what plugins are installed in your project).

Writing a plugin

Declare a top-level sigx-cli field in your package.json pointing at your plugin module:

{
    "sigx-cli": { "plugin": "./dist/plugin.js", "requires": ">=0.4.0" }
}

…and default-export a plugin from that module. Args declared with the a builders type ctx.args automatically — no casts:

import { a, definePlugin } from '@sigx/cli/plugin';

export default definePlugin({
    name: 'my-tool',
    detect: (cwd) => true,
    commands: {
        dev: {
            description: 'Start the dev server',
            aliases: ['d'],                    // optional alternate names
            args: {
                port: a.number().alias('p').default(8788),
                open: a.boolean(),
            },
            run: async (ctx) => {
                ctx.args.port;                 // number — inferred from the builders
                ctx.args.open;                 // boolean | undefined
            },
        },
    },
});

Commands can also set hidden: true (dispatchable but not listed in --help) and allowUnknownFlags: true (unrecognized flags land in ctx.unknownFlags instead of erroring). For a command authored in its own file, wrap it in defineCommand({...}) to keep the same ctx.args inference. Full plugin API → https://sigx.dev/cli/

License

MIT — © Andreas Ekdahl