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

spross

v0.0.12-alpha.2

Published

Spross - Interface overlays that 'sprout' from elements

Readme

Spross - Interface overlays that 'sprout' from elements

About Spross

Background

I've been struggling with the design language in our business.

When I want to refine it properly, I find myself torn between modifying individual components one by one or starting a full redesign of the entire design language.

For now, I’ve taken a middle-ground approach — I tend to use a verb to encapsulate certain components with similar behaviors, and that’s where 'Spross' comes from (it means 'sprout' in German).

I’m not deliberately using another foreign language, it’s just that registering a unique npm package is really challenging.

Similarly, I created another library called Springen.

So spross, as a design system concept, describes lightweight, contextually triggered components that dynamically grow from other elements.

Purpose

Of course, I don’t want to create components that feel outdated. I want each repetition to at least be infused with new creativity. Therefore, they should either have interesting features or be a result of my rethinking of best practices.