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.2.8

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 entry point for everything: scaffolding, dev servers, builds, previews, and platform-specific commands provided by plugins.

Commands

| Command | Provided by | Description | |---|---|---| | sigx create [name] | core | Scaffold a new project (interactive TUI; falls back to flag-driven headless when stdout isn't a TTY or when --yes / --type is passed) | | sigx info | core | Print environment & project info (Node, pnpm, installed @sigx/* packages, Lynx toolchain) | | sigx dev | @sigx/vite plugin | Start the Vite dev server (web) | | sigx build | @sigx/vite plugin | Production build (web) | | sigx preview | @sigx/ssg plugin | Serve a built SSG site | | sigx prebuild | @sigx/lynx-cli | Generate native iOS/Android project files | | sigx run:android | @sigx/lynx-cli | Build & launch on Android | | sigx run:ios | @sigx/lynx-cli | Build & launch on iOS | | sigx doctor | @sigx/lynx-cli | Verify Lynx toolchain (rspeedy, ADB, Xcode, JDK) |

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

Headless create (CI / scripts)

sigx create my-app --type basic                      # web SPA
sigx create my-app --type ssr  --styling tailwind    # SSR + Tailwind
sigx create my-app --type ssg  --styling daisyui     # SSG + Tailwind + daisyUI
sigx create my-app --type lynx --styling tailwind    # native mobile (Lynx)

Valid values:

  • --type: basic | ssr | ssg | lynx
  • --styling: none | tailwind | daisyui (daisyUI not available for lynx)
  • --yes / -y: skip prompts even when running in a TTY

Headless mode is also auto-selected when stdin/stdout is not a TTY (e.g. CI runners).

Plugins

Any package can extend sigx with new commands. To author a plugin, ship a sigx-cli.plugin field in your package.json pointing at a module that default-exports a SigxPlugin:

{
  "name": "my-sigx-plugin",
  "sigx-cli": { "plugin": "./dist/plugin.js" }
}
// my-sigx-plugin/src/plugin.ts
import type { SigxPlugin } from '@sigx/cli/plugin';

export default {
    name: 'my-plugin',
    commands: {
        hello: {
            description: 'Say hello',
            async run({ cwd, args, logger }) {
                logger.info(`hello from ${cwd}`);
            },
        },
    },
} satisfies SigxPlugin;

Plugins are discovered by walking up from cwd and inspecting installed dependencies' package.json files for the sigx-cli.plugin key.

License

MIT — © Andreas Ekdahl