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

@upbound/monarch-core

v0.9.1

Published

Upbound's design system — primitive components.

Downloads

2,274

Vulnerabilities

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

Links

Git

Maintainers

nicholas.thomson.upboundnicholas.thomson.upboundalex-upboundalex-upboundthephredthephreddechegaraydechegarayupbound-devopsupbound-devops

Keywords

Readme

@upbound/monarch-core

Upbound's design system — primitive components. Radix UI/Base UI-backed building blocks (Button, Dialog, Select, Sidebar, and 60+ more) with Monarch's tokens and theming baked in.

Deliberately dependency-light: no charting, no table state, nothing beyond what a primitive component genuinely needs. For composed, heavier components (charts, data tables, filter bars), see @upbound/monarch-blocks.

Install

npm install @upbound/monarch-core

Peer dependencies: react and react-dom (^18.3.0 || ^19.0.0), tailwindcss (^4.0.0).

Set up the theme

Two additions to your Tailwind entry CSS — both required:

@import 'tailwindcss';
@import '@upbound/monarch-core/theme.css';
@source '../../node_modules/@upbound/monarch-core/dist/*.js';

(Path assumes a Next.js --src-dir layout, where your Tailwind entry CSS lives at src/app/globals.css — two directories above your project root, where node_modules sits. Adjust to match wherever your own entry CSS actually lives.)

  • @import "@upbound/monarch-core/theme.css" pulls in Monarch's design tokens, dark-mode values, and the base-layer rules a handful of components rely on for correct rendering (e.g. ButtonGroup's border-merging).
  • @source tells Tailwind v4's JIT scanner to look inside this package's compiled files for the utility classnames used in component classNames (bg-primary, text-h1, etc.). Without it, Tailwind never generates CSS for those classes — they only exist inside node_modules, outside Tailwind's default scan root. Use dist/*.js (not a recursive dist/**/*.js or **/*.js) — a recursive glob silently matches nothing under Next.js's Turbopack Tailwind integration; a single-level glob works and is sufficient since every compiled file sits directly in dist/, with no subdirectories.

Fonts

theme.css references --font-inter and --font-outfit but doesn't ship font files — by default both fall back to a system-font stack, so components render correctly with zero setup. To get Monarch's exact Inter/Outfit branding, load those fonts yourself (next/font, a Google Fonts <link>, self-hosted @font-face) and set the two CSS variables on :root or <html>; your setup will win over the built-in fallback automatically.

Dark mode

Add a .dark class anywhere up the tree (<html>, <body>, or a scoped wrapper) to switch themes — no separate dark-mode setup needed. Pair with next-themes or your own toggle.

Use a component

import { Button } from '@upbound/monarch-core';

export function Example() {
  return <Button>Click me</Button>;
}

Or import a single component's own subpath — guarantees per-file tree-shaking regardless of your bundler:

import { Button } from '@upbound/monarch-core/button';

Server Components

The root barrel (@upbound/monarch-core) bundles all 67 components into one file and is a client boundary unconditionally — some components need client-side React, and a single file can't be client for some exports and not others. If you need a guaranteed-server-safe component in a Server Component tree, import its own subpath instead of the barrel:

// Always safe in a Server Component — no client boundary crossed.
import { Skeleton } from '@upbound/monarch-core/skeleton';

Also available via shadcn

Prefer to own the source in your own repo instead of installing a package? Every component here is also available through the shadcn CLI, once your project's components.json points its registries at Monarch's registry — see the main docs site for the full setup. Both channels ship the same components; pick whichever fits your project.