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

@hybridcore/ui

v1.6.13

Published

Hybrid Core UI Library

Downloads

2,559

Readme

Hybrid Core UI Lib

This library contains ui components which are developed based on Material UI v5.

Install

Install package with yarn

yarn add @hybridcore/ui

or with npm

npm install @hybridcore/ui

Develop locally

Component iteration via Storybook

For tight visual loops on a single component, no consumer project required:

yarn dev          # opens the Vite dev server with Storybook

Iterate against a real consumer (e.g. Smart Navigator) without publishing

We use yalc to link the lib into consumer projects locally, so changes show up in their dev server without a yarn version + npm publish round trip. Full rationale and gotchas in docs/plans/local-dev-flow.md.

One-time setup (per machine):

npm i -g yalc

Daily workflow — two terminals, two commands:

# terminal 1 — lib: rebuild + auto-push to every linked consumer on each save
cd shared/ui && yarn build:push
# terminal 2 — consumer (Smart Navigator): link the lib, then run the dev
# server under a watcher that auto-restarts on every yalc push
cd SmartNavigator/frontend && yarn link:ui && yarn dev:lib

Edit any file under lib/components/… → vite rebuilds → yalc push fires automatically → the consumer's dev:lib watcher detects the push, wipes Umi's mfsu cache, and restarts max dev. Browser auto-reloads. No manual rebuilds, pushes, or cache wipes.

Script reference

| Script | What it does | | ------------------- | -------------------------------------------------------------------------------------------------- | | yarn build | One-shot prod build (used by prepublishOnly). Does not push to yalc. | | yarn build:watch | vite build --watch only — re-rolls dist/ and types on each save. Does not push to yalc. | | yarn build:push | Same as build:watch plus an auto-yalc push after every successful rebuild. Use this for dev. |

The auto-push hook is implemented as a closeBundle plugin in vite.config.ts, gated by the YALC_PUSH=1 env var that the build:push script sets. yarn build stays pure so npm publishes never accidentally push to local consumers.

To register the lib in a consumer project for the first time, run yalc add @hybridcore/ui once inside the consumer. The Smart Navigator frontend wraps this in a yarn link:ui script — see its README.

Release

Versioning + publish is handled by the Azure pipeline. The prepublishOnly hook runs yarn build, so always commit a clean working tree before bumping.

yarn version patch    # or minor / major
git push --follow-tags

Documentation

  • docs/COMPONENT_GUIDE.md — authoring rules (4-file structure, HC* prefix, theme augmentation block)
  • docs/THEMING.md — consumer-facing override guide for any project using this lib
  • docs/plans/ — cross-cutting initiative plans (e.g. local dev flow, exports standard)