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

jbx

v2.15.0

Published

The little component toolkit behind the tools on javier.xyz. Plain components with a class each, one stylesheet, no runtime dependencies.

Readme

JBX

The little component toolkit behind the tools on javier.xyz. Plain components with a class each, one stylesheet, no runtime dependencies.

pnpm add jbx

React is a peer dependency (17, 18 or 19), so it uses whichever copy you already have.

Styles

Either import the stylesheet and set your own accent color:

import 'jbx/main.css';
:root {
  --accent-color: #f1c40f;
}

Or let the JBX component do both:

<JBX accent="#f1c40f" />

JBX has no hooks and no dependencies, so it renders inside a React server component too. So does every component except Input, which holds the state behind onValueChange and is marked 'use client'.

Two more variables are worth knowing about. --control-height is how tall a Button, Input or Range stands on its own; --control-height-compact is what one shrinks to inside a Tabs row, where it matches the line box of the text beside it so the row is no taller than a row of plain tabs.

Use

import { JBX, MainHeader, Text, Space, Container } from 'jbx';

function App() {
  return (
    <Container>
      <JBX accent="#f1c40f" />
      <MainHeader>React Blur</MainHeader>
      <Space h={1} />
      <Text>React component for creating blurred backgrounds.</Text>
    </Container>
  );
}

Components

Layout: Container, Inline, Stack, Box, Space.

Type: MainHeader, HeaderH1--HeaderH4, Text, SmallText, A, Ul, Li, Bullet, HR.

Controls: Button, Input, Range, Checkbox, Tabs with Tab, Dropzone.

Code: CodeSnippet, CodeTextarea.

Plus JBX for the stylesheet, MoreExperiments for the footer that links the other tools, and Component and space for building your own.

Number inputs

Input is a plain controlled input until you hand it onValueChange, which switches it to numbers and takes over the awkward part: it holds what was typed and only calls you back once that parses and lands inside min/max. A half typed value never reaches your state, so nothing downstream jumps around mid-keystroke, and blurring a field you left half typed restores the live value.

<Input value={seconds} onValueChange={secondsSet} min={0.2} max={60} step="0.5" />

value and onChange on their own behave exactly as they always did.

Spacing

Everything is measured in units of --size (16px, 14px on smaller screens). <Space h={2} />, <Inline gap={1} />, <Box padding={[0.5, 1]} /> all speak the same scale, and space(n) gives you the raw css value if you need it somewhere else.

Making your own

Component is the whole idea — a class name, optional styles, optional element:

const Sprite = Component(
  `jbx-img`,
  ({ height, width }) => ({ height, width, imageRendering: 'pixelated' }),
  { element: 'img', styleProps: ['height', 'width'] }
);

styleProps lists the props the style function consumes so they don't end up as DOM attributes.

Develop

pnpm dev            # serve the interactive preview at localhost:3008/jbx
pnpm dev:lib        # rebuild the published library on change
pnpm preview:build  # make a production build of the preview
pnpm typecheck
pnpm test           # renders every export, fails on any React warning

Publish

New versions are published to npm automatically when they reach main. A push whose version is already on npm succeeds without publishing again.

  1. Add the release notes to CHANGELOG.md.
  2. Run pnpm version minor --no-git-tag-version to update package.json.
  3. Run pnpm test.
  4. Commit the changes and push them to main.
  5. Confirm the Publish package workflow succeeds, then check the version with pnpm view jbx version.

Publishing uses npm trusted publishing through GitHub Actions. It does not require an npm token in the repository.