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

@protolabsai/ui-css

v0.73.0

Published

protoLabs.studio component stylesheet — the .pl-* classes from @protolabsai/ui, with no React runtime. Pairs with @protolabsai/design tokens.

Readme

@protolabsai/ui-css

The protoLabs.studio component stylesheet — every .pl-* class from @protolabsai/ui, with no React runtime.

Pairs with @protolabsai/design for the --pl-* tokens the classes read. Those two packages are the whole CSS story:

| package | ships | | ---------------------- | ------------------------------------------------ | | @protolabsai/design | the --pl-* tokens + the element base layer | | @protolabsai/ui-css | the .pl-* component classes (this package) | | @protolabsai/ui | the React components that render those classes |

Use

For a project that does not render the React components — an Astro or Eleventy site, a server-rendered template, a plain HTML page built with a bundler:

@import "@protolabsai/design/css"; /* tokens + base layer */
@import "@protolabsai/ui-css"; /* component classes */

That installs two packages and zero React.

If you do use the React components, you don't need this package in your manifest — import "@protolabsai/ui/styles.css" forwards here, and @protolabsai/ui depends on it. Both paths load byte-identical CSS.

Why it's a separate package

@protolabsai/ui declares react/react-dom as peer dependencies and carries 15 runtime dependencies (Radix, dnd-kit, framer-motion, streamdown, …). npm 7+ auto-installs peers, so a project importing the library only for its stylesheet still got React, react-dom, scheduler and all 15 in its tree — and protoAgent's React-free marketing site broke on npm ci because of it (protoContent#495, protoAgent#2875). Splitting the CSS out removes the coupling at the root rather than trimming it.

react-free.test.mjs guards the invariant: this package's dependency closure must stay React-free, and @protolabsai/design at the floor of it must stay dependency-free.

Versioning

@protolabsai/ui-css and @protolabsai/ui are a fixed changesets group — they always publish the same version, so a component change and the CSS it needs never ship under versions you have to cross-reference. It starts at 0.59.2 to match the @protolabsai/ui it was split out of.

Partials

styles.css is an @import barrel over styles/*.css, one file per component domain. Order matters: touch.css is last on purpose — the touch floor overrides component defaults through source order rather than !important.