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

cl-react-tailblocks

v0.0.8

Published

Tailblocks implementation in React + TypeScript

Readme

cl-react-tailblocks

TypeScript implementation of Tailblocks components.

All components supports a light and dark theme as well as these colors: indigo | yellow | red | purple | pink | blue | green

Tailblocks components that are not implemented are specified in the MISSING file.

Install

react, react-dom and tailwindcss are peerDependencies and are thus expected to already be in your project.

yarn add cl-react-tailblocks

Why?

Mert Cukuren made this wonderful repository that I utilize and it's great. However, copy/pasting each time in each project, making it jsx, modifying the content and so on, can be very repetitive. Thus, I made this library, that allows to simply import the component you want with the properties you need.

Docs

The only form of documentation for now is via storybook, which is located here here or an example repository located here.

However, a few patterns are as follows:

Theme

You can specify a global theme using React.Context. A ThemeContextProvider is exposed and can be used for this purpose. On top of that, each component takes two optional props: theme and color.

  • If no provider is used and no theme props are specified, the default values are light and indigo.

  • If a provider is used and no theme props are specified, the provider context will be used.

  • If a provider is used and theme props specified, the theme props will override the context for that specific component.

Nodes

Some props, such as links, images, svgs and so on, always allows for an optional node that should contain a React.ReactNode - or in some cases a function that returns a React.ReactNode. This will override the default node, allowing for decent component customization.

The pattern is that all of those optional node props will have property names that end on Node and be prefixed with it's context. So a custom node for a link, will always have the property name linkNode, for an svg it will always be svgNode and so on.