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

@cagovweb/design-system

v0.2.0

Published

This system makes it easy to build digital services that meet the needs of Californians.

Vulnerabilities

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

Links

Maintainers

carter.medlincarter.medlinjon-grantjon-grantguzmanjdguzmanjdkkoryakakkoryakaxjensenxjensen

Keywords

Readme

California Design System

The Design System test site

This is the Base Team repository for the upcoming California Design System. We can make this readme professional later. For now, here's what devs need to know.

Grab it

There are currently two ways to grab the latest code from this repository. Take your pick.

We plan to support CDN-based download options in the future.

Install from NPM

From your JavaScript project folder, run the following.

npm install @cagovweb/design-system

For now, the files will be available in node_modules/@cagovweb/design-system/dist.

We'll make this more convenient as we learn more about how people want to consume this code from the NPM package.

Source

All CSS and JavaScript source can be found in their respective src subfolders.

Pages

The pages folder is a place to test your work.

Development

The repository currently uses 11ty for page previews. To run it...

  1. Clone this repository.
  2. Run npm install.
  3. Run npm run start.
  4. Point your browser to the URL that appears in the terminal, probably localhost:8080.

Build the 11ty site

To build the 11ty site files, run npm run site.

Files will be written to the _site folder.

This is useful for uploading to GitHub Pages.

Build standalone bundle files

To build the CSS/JS bundle files, run npm run bundle.

Files will be written to the dist folder.

This is useful for packaging activities, such as GitHub Releases, NPM, and CDN.

Deprecated NPM packages

We previously published NPM packages in the 1.X.X series. Since then, we decided to republish as beta in 0.X.X. Therefore, several npm packages from the past work have been deprecated, to prevent stale downloads while we're still in beta.

To bring those packages back and remove the deprecation warning, run the following command.

npm deprecate @cagovweb/[email protected] ""

npm deprecate @cagovweb/[email protected] "The Design System is currently in beta. This post-1.0 package is an artifact of past work. It does not represent the latest progress on this project."

The following package version numbers apply.

  • 1.1.0
  • 1.2.0
  • 1.3.1
  • 1.4.0
  • 1.5.0
  • 1.6.0

See more at npm's deprecation page.