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

@antjanus/cottage-ui

v2.0.0

Published

React component library with cottage-style UI primitives for consistent, accessible interfaces.

Downloads

268

Vulnerabilities

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

Links

Git

Maintainers

antjanusantjanus

Keywords

Readme

Cottage UI

A React component library built with TypeScript, TailwindCSS, and Vite. Created as part of the Build A React UI Library series.

Demo

Cottage UI Components

Features

  • TypeScript-first component library
  • TailwindCSS utility styling
  • ESM + UMD bundles
  • Vitest + React Testing Library coverage
  • Storybook docs with @storybook/react-vite
  • Bundled type declarations

Installation

npm install @antjanus/cottage-ui

Usage

import { Button, BUTTON_VARIANTS, BUTTON_SIZES } from '@antjanus/cottage-ui'
import '@antjanus/cottage-ui/dist/cottage-ui.css'

function App() {
	return (
		<Button
			variant={BUTTON_VARIANTS.PRIMARY}
			size={BUTTON_SIZES.LARGE}
			onClick={() => console.log('Clicked!')}
		>
			Click me
		</Button>
	)
}

Theming

Cottage UI ships four themes — cottage (the signature AJ palette: warm clay, amber, pine & teal), graphite, evergreen, and bloom — each with a light and dark mode. Components are styled by semantic role, so switching theme recolors the whole library.

Set data-theme (and optionally data-mode="dark") on any ancestor element:

<html data-theme="cottage">              <!-- light, default theme -->
<html data-theme="graphite" data-mode="dark">

With no attributes set, the default is cottage / light. Switch at runtime by updating the attributes:

document.documentElement.dataset.theme = 'evergreen'
document.documentElement.dataset.mode = 'dark'

Status -strong-on--soft pairs (badges, alerts) are WCAG AA verified in both modes. The local demo (npm run dev) includes a theme/mode switcher and a palette showcase.

Development

This repo uses npm.

npm install
npm run dev
npm run storybook
npm run lint
npm run test -- --run
npm run build

Project Layout

cottage-ui/
├── lib/                  # Published library source
├── src/                  # Local demo app
├── .storybook/           # Storybook config
└── dist/                 # Build outputs

Contributing

  1. Add or update code in lib/
  2. Add/adjust tests and stories
  3. Export new APIs in lib/main.ts
  4. Run lint, tests, and build before opening a PR

Documentation

License

MIT. See LICENSE.

Contributing

See CONTRIBUTING guidelines: add code in lib/, add tests and stories, export from lib/main.ts, then run lint/test/build before opening a PR.