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

@haiticss/haiticss

v1.0.0-alpha

Published

Just another baseline perspective to wear any project with the ITCSS architecture

Readme

:pineapple: haiticss

Build Status

Just another baseline perspective to wear any project with the ITCSS architecture. Mainly based on the excellent project inuitcss by Harry Roberts, from where I found my best suitable starting point.

The idea to create this project, comes from the necessity to adding some modifications and missing features on INUIT that probably will not fit into the original project roadmap.

The input of this mutation comes from my experience applying this architecture on many projects, some new, some not.

Main differences from inuitcss are:

  • Number prefixes on CSS layers, helping non familiar developers to get into the architecture hierarchy.
  • Namespaced variables to improve compatibility when importing into an existent project.
  • Scoped version of generic layer, helping to start old site migrations on the fly, respecting the legacy code, but breaking most risky inheritance.
  • Feature toggling variables to include/exclude any object or utility.
  • Extended objects and utilities configuration variables to toggle and configure some modifiers groups and unused CSS output.

References