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

@frontendfixer/stylelint-config-standard

v1.0.1

Published

Stylelint config with standard rules and useful plugins

Downloads

1

Readme

@frontendfixer/stylelint-config-standard

npm GitHub Workflow Status (with event) GitHub

Stylelint config with standard rules and useful plugins


Packages included


Usages

Installation

yarn add -D postcss^8.4.27 stylelint^15.10.2 @frontendfixer/stylelint-config-standard

Configuration

Create a Stylelint config file with .stylelintrc or .stylelintrc.json and put this lint

{
  "extends": "@frontendfixer/stylelint-config-standard"
}

or you can also put it in your package.json above scripts or higher position

"stylelint": {
    "extends": "@frontendfixer/stylelint-config-standard"
  }

Add script

You can add two scripts to your package.json to lint and/or fix:

"scripts": {
  "lint": "stylelint '**/*.{css,scss}'",
  "lint:fix": "stylelint '**/*.{css,scss}' --fix",
},
  • Now you can manually lint your code by running yarn run lint and fix all fixable issues with yarn run lint:fix. You probably want your editor to do this though.

Auto fix lint error with VSCode

You should read this entire thing. Serious!

Once you have done one, or both, of the above installs. You probably want your editor to lint and fix for you. Here are the instructions for VS Code:

  1. Install the vscode-stylelint
  2. Now we need to setup some VS Code settings via Code/FilePreferencesSettings. It's easier to enter these settings while editing the settings.json file, so click the Open (Open Settings) icon in the top right corner:
// disable the built-in CSS, Less, and SCSS linters:
"css.validate": false,
"scss.validate": false,
// enable stylelint
"stylelint.validate": ["css", "scss"],
// tell the Stylelint plugin to run on save
"editor.codeActionsOnSave": {
  "source.fixAll.stylelint": true
},