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

@roadline/styles

v0.2.0

Published

Optional default theme for Roadline, built entirely on CSS custom properties.

Readme

@roadline/styles

The optional default theme for Roadline.

npm install @roadline/styles
import '@roadline/styles/roadline.css'

That is the whole theme in one file. It is assembled from one file per area, and each part is importable on its own — @roadline/styles/tokens.css for the palette alone, @roadline/styles/reset.css and root.css for the load-bearing layout rules, and so on per component.

Everything it paints is a CSS custom property, so restyling is a variable override rather than a selector war:

.rl-root {
  --rl-bar: #6366f1;
  --rl-accent: #f43f5e;
  --rl-radius: 8px;
}

Light and dark ship as one palette written with light-dark(), following the operating system out of the box. To pin a theme, set color-scheme from your app — .dark .rl-root { color-scheme: dark; } — which also brings native scrollbars along.

Skip this package entirely and the components still work, laid out but unpainted; nothing in the JavaScript knows what anything should look like. Two rules are load-bearing if you write your own stylesheet:

.rl-bars { pointer-events: none; }  /* dragging empty canvas pans */
.rl-bar  { pointer-events: auto; }

Full token and class reference: docs/theming.md in the repository.

MIT