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

v0.7.0

Published

SignalX - Lightweight reactive component framework with signals and TSX support

Readme

SignalX

Lightweight reactive component framework with signals and TSX support. This is the main entry point that re-exports the public API from @sigx/reactivity, @sigx/runtime-core, and @sigx/runtime-dom.

📚 Full guides, API reference and live examples → https://sigx.dev/core/

Install

npm install sigx

Usage

import { component, signal, render } from 'sigx';

const Counter = component(() => {
  const count = signal(0);

  return () => (
    <div>
      <p>Count: {count.value}</p>
      <button onClick={() => count.value++}>Increment</button>
    </div>
  );
});

render(<Counter />, document.getElementById('app')!);

📚 Documentation

Full guides, the complete API reference and live examples → https://sigx.dev/core/

License

MIT

Development vs production builds

Every sigx package ships two builds: the development build (helpful warnings + devtools support) and a production build with all of that compiled out. Your bundler picks the right one automatically via the development/production export conditions — Vite needs no configuration. Running plain Node (SSR) without a bundler? The development build is the default and checks process.env.NODE_ENV at runtime; use node --conditions=production to get the stripped build.