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 🙏

© 2024 – Pkg Stats / Ryan Hefner

petricorcss

v1.2.0

Published

CSS/SCSS utility framework

Downloads

5

Readme

Petricor CSS 💦

Petricor CSS is an utility library for building web interfaces. It’s build in SASS and provides a full collection of utility classes that helps you work faster and apply css without almost switching between css and html. It's heavily influenced by Tailwind CSS.

Key concepts

Wide collection of tiny utility classes

Detaching properties into tiny functional classes makes your code more reusable, less dependent and portable. Having classes doing too much leads to scalable issues in the middle-long term.

Remove the process of thinking about naming your classes or adopting nomenclatures like BEM. No more abstract class names that need new modifiers to accommodate similar looking components. You’ll know exactly what they’re doing by just looking at them. Your components will be self-descriptive.

Low specifity

As a general rule the majority of classes have a specificity as low as 0,0,1,0. Specificity wars with !important won’t bother you anymore. There are some fewer exceptions where it does make sense to take advantage of the cascade. For those specific cases the specificity will increase up to 0,0,2,0.

Made to be customized

All these utilities are generated from a single source of truth. A config file with sass maps containing presets for spacings, colors, typography, box-shadows, transforms, etc.

CSS authors can extend, modify, enable or disable utilities and variants. Customizing Petricor CSS is really easy and you can do so without modifying the core library. This way you can update to new versions without loosing your setup.