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

@lexydesign/amatista

v0.1.0

Published

React 18+ component library for the LexyDesign Amatista design system.

Readme

@lexydesign/amatista

React component library for the LexyDesign/Amatista UI system.

The package entrypoint is lib/index.ts. It imports the base CSS and re-exports the public component API from lib/components/index.ts.

Install

pnpm install

Development

pnpm storybook

Storybook reads stories from lib/**/*.stories.@(js|jsx|mjs|ts|tsx).

Tokens

This package uses Tailwind CSS v4 and loads Lexy tokens from lib/tokens.css. The token file is generated from the Kickoff template source, so do not edit it by hand.

pnpm sync:tokens

The sync command reads /home/obarria/Escritorio/Dev/kickoff-cli/template/src/app/globals.css, extracts the real @theme block, and writes lib/tokens.css.

Public API

The public API is generated. Do not edit lib/components/index.ts by hand.

pnpm sync:public-api
pnpm check:public-api

Public components are listed in scripts/public-components.mjs. Internal implementation details live under lib/vendor and should not be exported directly from the package entrypoint.

Validation

pnpm validate
pnpm build-storybook
pnpm verify:storybook-css

pnpm validate runs the library audit, public API check, tests, and package build. pnpm verify:storybook-css validates that every documented LexyDesign Storybook route renders with effective CSS and writes visual reports under reports/.

Audit

pnpm audit:library

The audit writes reports/library-audit.json and reports:

  • public component count
  • missing stories
  • missing specs
  • unclassified component folders
  • empty component folders

Build

pnpm build

Build output is written to dist. Storybook static output is written to storybook-static; both are generated artifacts.

Publish To npm

The package is configured for public npm publishing as @lexydesign/amatista.

Before publishing, authenticate with npm using an account that has access to the @lexydesign scope:

npm login
npm whoami

Run the full release gate:

pnpm release:check

Create a local tarball for inspection:

pnpm release:pack

Inspect the exact files npm will publish:

npm pack --dry-run

Publish the current version:

pnpm publish

For future releases, bump the version first:

pnpm version patch
pnpm publish

The prepublishOnly script runs pnpm release:check, so npm publication fails if the library audit, public API check, tests, package build, Storybook build, or CSS verification fails.