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

@xenosystem/elements-react

v0.0.10

Published

The XENO web renderer — interprets element declarations as React/SVG. CSS-first, 0 kb runtime.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

emilianbnkrsysemilianbnkrsys

Keywords

Readme

@xenosystem/elements-react

Web + Electron renderer

Status: 🔵 planned — see ../../SPEC.md §13 for the build order.

Interprets @xenosystem/elements declarations as React components and web components.

Not built yet — Phase 2. The contract lands first, deliberately (SPEC.md §13).

When it is built, it must

  1. Honour every declared axis. Silently ignoring one produces an element that looks interactive and isn't — the worst failure in the set.
  2. Never invent state. No pressed binding in the declaration means pressed looks like idle.
  3. Map input modalities per docs/STATE-MODEL.md §3 — including the agent row, or agent-driven UI diverges from what a human would have seen.
  4. Be visually indistinguishable from every other renderer given the same declaration. Testable, and tested.
  5. Add nothing. No renderer-local colours, timings or easing.

Hard constraints

  • CSS-first, 0 kb runtime. Axes become data-* attributes; bindings become CSS custom properties and transitions. This diverges from the 2026 norm (@animateicons, LivelyIcons, Itshover all build on motion/react) because XENO elements must run inside sandboxed iframes and survive web export, where a JS animation runtime is weight in every sandbox and a dependency that cannot be removed later.
  • motion is an opt-in entry point only (/motion), for genuinely orchestrated cases — multi-step morphs, physics. ~4.6 kb with m + LazyMotion vs 34 kb naive. Never a dependency of the base renderer.
  • No barrel. Per-element entry points, sideEffects: false. A single index importing everything is why lucide-react is 2.4 MB — and lucide-react/dynamic collapses to an empty chunk in production builds.
  • Base UI is an implementation detail here, used for composite behaviour and accessibility. It is never exposed as the system's foundation. (Radix stalled after the WorkOS acquisition; Base UI reached v1.0 in Dec 2025 with full-time MUI engineering.)
  • Components are generated, never hand-written. Editing one to fix a glyph means the declaration is wrong.

Part of xeno-elements. Visual authority: DESIGN_SYSTEM.md — LOCKED.