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

classless-js

v0.1.10

Published

Enforce and question your design system by checking your classes against an approved class list

Downloads

15

Readme

Classless.js

One of the biggest reasons design systems become outdated is because of enforcement and lack of updating. Classless solves all of that! The way it works is by comparing your markup to your existing design system file. If there are additional classes added, Classless will alert you to either check the design system or add it to the approved class list. This makes us pause in our development and ask two questions:

  1. Do we really need this additional class or does it already exist?
  2. Should I contribute this back to the design system or is it truly a one-off?

It also creates a list of elements that we've introduced in this project (in time-based order if adding classes to the bottom of the list), to make refactoring easier.

Classless makes sure you use less unique classes in your project and instead implement your design system to its fullest potential.

Setup

  • globally install classless with npm install -g classless-js
  • at your root directory, touch classless.config & set it up with options
  • run classless in your CLI once this is set up in your project

Options

classless.config per-project options:

  • cssPath: Link to your CSS stylesheet(s) -- You can link to a directory of files, but compiled CSS works best because this doesn't take into account things like Sass mixins, etc. Examples: ./bower_components/unicornDesignSystem/app/**/*.scss or css/**/*
  • htmlPath: Link to your HTML path(s). Can be any format (i.e. .erb, .hbs, etc.)
  • acceptedElems: Additional accepted elements list

Contributing

The /bin folder is where all of the executable scripts live. Please update and submit a PR.