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 🙏

© 2025 – Pkg Stats / Ryan Hefner

plantcss

v0.0.1

Published

Spend more time designing and less time configuring.

Readme

🌱 plant.css

Experimental

Spend more time designing in the browser and less time configuring.

Note: this is just an idea right now. Feel free to make issues/PRs to help refine it.

Concept

This could turn out to be horrible idea, but bear with me — we can try it out and see if it goes anywhere. Yes, this is yet another utility css toolkit. As a longtime user of functional css here are some things I’ve noticed:

  • Functional css is great.
  • Utility generation is awesome (i.e. tools like tachyons-generator or Tailwind).
  • Being able to customize your utility names to your own liking: even better.
  • Do I need all the utilities that are generated: hard no — in fact never.
  • So we use tools like purgecss to remove unused styles.

The basic concept:

write HTML and add class names and plant will create the styles as you go.

Remember: potentially a bad idea. Plant will scan your documents for classnames and match it with utilities it knows how to create.

Also, let's add some intelligence: plant will suggest component extractions are you go. Perhaps you keep using the same classes together? Plant will notice and let you know. Perhaps it will even let you know much bytes you will lose or save if you do so.

A major goal with plant is that you set your design system (i.e. colors, type scale, breakpoints, etc.), flavour of utility class (I prefer Tachyons' terseness), and path to HTML/PHP, and then you never need to configure it again.

Here are some fun names we can use for things:

  • seed = utility
  • flower = component

Goals

For now the first goal is 0.1.0 a basic functioning example.

Inspiration

License

MIT License