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

@bysages/core

v0.1.2

Published

Shared core of By Sages Elements — theme engine, per-component styles, and the lighting engine, all token-driven

Readme

@bysages/core

npm version npm downloads npm license

The visual core of By Sages Elements: the only style layer of the design system, the theme engine, and the lighting engine — framework-agnostic, consumed by every wrapper package.

Features

  • 🎨 The only visual layer — every component's stylesheet lives here, native CSS scoped by [data-scope][data-part], so one stylesheet serves React, Vue, Solid, and Svelte alike
  • 🌗 Theme engineapplyTheme() drives light/dark, accent pigments (qinghua / celadon / zhusha), contrast tiers, density tiers, and scene presets, all expressed as data on the document root
  • 💡 Lighting engine — elevation, pigment bleed, and pointer-carried light computed into CSS variables (setLight, attachDynamicLight); component styles only ever consume light (以光为影 — light as shadow)
  • 🖋️ Ink ripple — a press feedback pass that bleeds pigment from the pointer, delegated at the root and tuneable per element
  • 🧩 Style injectioninjectComponentStyle() ships each family's stylesheet at import time, guarded by a head marker so SSR builds that inline styles never double-inject

Installation

# pnpm
pnpm add @bysages/core @bysages/tokens

# npm
npm install @bysages/core @bysages/tokens

# yarn
yarn add @bysages/core @bysages/tokens

# bun
bun add @bysages/core @bysages/tokens

Quick Start

Load the compiled tokens, theme the document, and the component styles arrive with the wrappers:

import "@bysages/tokens/css";
import { applyTheme, attachDynamicLight } from "@bysages/core";

applyTheme({ mode: "system", accent: "ink", density: "default" });
attachDynamicLight();

Architecture

@bysages/tokens    DTCG source → CSS custom properties
      ↓
@bysages/core      theme engine · lighting engine · per-component styles
      ↓
wrappers           Vue · React · Solid · Svelte — thin adapters over headless machines

The core owns no interaction; it renders nothing but light. Wrappers bring the headless state machines, the core dresses them.

License