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/lynx-zero

v0.11.0

Published

Design-system-neutral UI foundation for sigx-lynx — the shared props/token contract and style utilities that design-system packages (daisyui, heroui, …) build on

Downloads

2,290

Readme

@sigx/lynx-zero

Design-system-neutral UI foundation for sigx-lynx. Design-system packages (@sigx/lynx-daisyui, @sigx/lynx-heroui, …) build on it; apps normally import from their chosen design system, which re-exports what it uses from here.

📚 Documentation

Full guides, API reference and live examples → https://sigx.dev/lynx/modules/zero/overview/

What lives here (growing per the phases in signalxjs/lynx#219):

  • The shared contract (SizeScale, ColorVariant, ColorToken, common prop fragments like WithColor/WithDisabled/PressEvent) — the vocabulary every design system agrees on, so switching an app from one DS to another is mostly an import swap.
  • Token-name conventions — every theme resolves against the same CSS custom-property names (--color-*, --radius-*, --size-*, --text-*).
  • Style utilitiesresolveBoxStyle, resolveSpacing, resolveColorToken.
  • Press-feedback defaultsPRESSED_SCALE, PRESSED_OPACITY.
  • (Later phases) layout primitives (Row, Col, Center, Spacer, ScrollView) and the theme engine (ThemeProvider, themeController, theme registry).

What deliberately does not live here: visual components, component CSS, class-name recipes, theme palettes — those are per-design-system.