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

@prudencss/sass

v0.1.2

Published

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

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

joehannesjoehannes

Keywords

sassbemitcssbemit

Readme

:pineapple: haiticss

Build Status

Like others, haiticss is just another CSS framework to wear any project with the ITCSS architecture. Mainly inspired on the excellent project inuitcss by Harry Roberts, from where we found our best suitable starting point. If you plan to compare and choose other solutions, we suggest you to check iotaCSS and Nebula CSS as well.

The main idea that encouraged us to create this project, comes from the necessity to align a solid CSS architecture with a visual language and design collaboration workflow. We use it to build coherent and consistent interfaces, style guides and design systems. Works for both new projects and existing ones, no matter if you start from scratch or you inherited a legacy hell to improve or maintain. If you're looking for similar objectives, maybe you found a suitable starting point for your project.

In the end we added some layers, and a visual language into the architecture. Using it properly, should help you on building digital products right now, without complex setup neither architectural decisions. With haiticss you can easy be succeed in technical terms, but cherry on the cake comes first with design collaboration, and then spreading the language to all involved stakeholders.

Main differences from other similar frameworks are:

  • Number prefixes on CSS layers, helping non familiar developers to get into the architecture hierarchy (reconsidering to add again).
  • Abstract content, no components provided out of the box.
  • Design foundations, a visual language defined by close collaboration between developers and designers. Extensible and customizable.
  • Feature toggling variables to include/exclude any feature and prevent unused CSS output.
  • Objects served both as class based output and mixins as well. It lets you use the black magic on wayward conditions.
  • Added a material layer with configurable base elements.
  • Added an abstract animations layer.
  • Added a color schemes layer.
  • Scoped option built on settings and generic layers, helping to start old site migrations on the fly, respecting the legacy code, but breaking most risky inheritance.

References