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

stylelint-config-readable

v1.4.0

Published

Configuration for Stylelint to achieve readable source code.

Downloads

6

Readme

Stylelint Config ReadableSponsored by Version Dependencies

"If you want your code to be easy to write, make it easy to read." — Robert C. Martin

The aim of this configuration is to achieve optimal readable code for a large number of projects. In many cases, the easing of the code's looseness in comparison to its compactness is an advantage for this. The idea is that code is much more read than written. Clear and structured code is therefore valuable for each additional author.

The code should appear uniform no matter how many authors are involved. But of course, it is not only about formatting (which could be fully solved with new tools like Prettier) but also about avoiding errors and mentoring developers. As you will see the chosen infrastructure with ESLint as a backbone offers so much more.

There is also the matching ESLint Configuration available.

Features

  • Blocks usage of !important.
  • Correctly supports typical Sass dialects like @mixin.
  • Tolerates normalize PostCSS plugin for automatically cherry-pick required normalization features.
  • Tolerates CSS Modules composes feature.
  • Tolerates Lost Grid features.
  • Checks CSS animation/transition for performance issues.

Formatting

  • Use 2 spaces for indention
  • 80 characters max line length
  • Use lowercase properties, selectors, mixin names, etc. only
  • Requires property splitting between layout (position, margin, padding, size) and visuals (appearance, colors, animation)

Usage

Installation with npm:

npm install --save-dev stylelint-config-readable stylelint

Installation with yarn:

yarn add --dev stylelint-config-readable stylelint

Add the preset to your stylelint config e.g. .stylelintrc.yml

extends:
  - stylelint-config-readable

Though this configuration is meant to be usable without any further configuration you are naturally free to extend it and place overrides into your configuration e.g. by extending the rules section:

extends:
  - stylelint-config-readable
rules:
  indentation: 4

Copyright

Copyright 2015-2018Sebastian Software GmbH