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

@atme-lab/ui-kit

v0.1.18

Published

Component library for personal projects

Readme

@atme-lab/ui-kit

Component library for personal projects

Read in Russian

Installation

pnpm add @atme-lab/ui-kit
# or
npm install @atme-lab/ui-kit
# or
yarn add @atme-lab/ui-kit

Quick Start

import {
  ThemeProvider,
  lightTheme,
  Button,
  Typography,
} from "@atme-lab/ui-kit";
import "@atme-lab/ui-kit/styles.css";

function App() {
  return (
    <ThemeProvider theme={lightTheme}>
      <Typography variant="h1">Hello World</Typography>
      <Button variant="primary">Click me</Button>
    </ThemeProvider>
  );
}
import "@atme-lab/ui-kit/styles.css";

Component Documentation

Detailed documentation for all components, their props, and usage examples is available in Storybook.

To view documentation locally:

pnpm storybook

Or use the online documentation (if available).

Using Themes

The library provides two ready-made themes: lightTheme and darkTheme. You can use either of them or create your own custom theme.

Light Theme

import { ThemeProvider, lightTheme } from "@atme-lab/ui-kit";

<ThemeProvider theme={lightTheme}>{/* Your components */}</ThemeProvider>;

Dark Theme

import { ThemeProvider, darkTheme } from "@atme-lab/ui-kit";

<ThemeProvider theme={darkTheme}>{/* Your components */}</ThemeProvider>;

Custom Theme

import { ThemeProvider, lightTheme, mergeTheme } from "@atme-lab/ui-kit";

const customTheme = mergeTheme(lightTheme, {
  palette: {
    primary: {
      main: "#ff0000",
    },
  },
});

<ThemeProvider theme={customTheme}>{/* Your components */}</ThemeProvider>;

Available Components

The library includes the following component categories:

  • Primitives: Button, Typography, Tag, and other base components
  • Form: Input, Select, Checkbox, Radio, and other form components
  • Feedback: Alert, Toast, Modal, Tooltip, and other feedback components
  • Layout: Card, Container, Stack, Grid, and other layout components
  • Navigation: Tabs, Menu, Breadcrumb, and other navigation components

See the Storybook documentation for a complete list of components and usage examples.

Development

# Install dependencies
pnpm install

# Run Storybook
pnpm storybook

# Run tests
pnpm test

# Build
pnpm build

# Linting
pnpm lint

Versioning

The project uses Conventional Commits for automatic versioning and CHANGELOG generation.

Commit Format

All commits should follow the Conventional Commits format:

<type>: <subject>

[optional body]

[optional footer]

Breaking changes: For major version, add BREAKING CHANGE: in the commit footer or use ! after the type: feat!: breaking change

Creating Commits

Recommended way (interactive):

pnpm commit

Or use regular git commit with the correct format:

git commit -m "feat: add Button component"
git commit -m "fix: correct Input styles"

Creating a Release and Publishing to npm

1. Create a release (bump version, update CHANGELOG, create tag and commit):

# Auto version from commits (patch/minor/major)
pnpm release

# Or explicitly: minor
pnpm release:minor

# Or explicitly: major
pnpm release:major

2. Push changes and tags to the repository:

git push --follow-tags

3. Publish the package to npm:

pnpm publish

Before publishing, prepublishOnly runs → npm run build: the dist folder is built and only the built output is published (see the files field in package.json). No need to run build manually.

License

MIT