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

@hendotcat/elements

v0.0.5

Published

React component library

Readme

This project is an exploration of some ideas around React, TypeScript and HTML. For a while I've wondered if React & TypeScript can be used to facilitate generating valid, accessible HTML documents. So I made this to try it out.

The idea is that it should be impossible to render an invalid document if you use these components. Basic HTML accessibility issues such as skipping heading ranks should be impossible too. And pages that contain a mixture of content in different languages should have the minimal set of lang attributes necessary for screen readers to make sense of it all. That kind of thing.

It's been fun to explore the idea but I'm not convinced the result is worth it. It needs a lot of meta-programming and a lot of functional programming indirection. And it gets a little busy with all the context providers, to the extent that I'd be concerned about client-side performance if this code was used for anything other than server-side rendering.

So that's probably that for this project, but the repo gets to stay online anyway just in case I want to borrow code or ideas from it.