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-sonarqube

v1.0.3

Published

A stylelint config that attempts to map sonar css rules to stylelint rules.

Downloads

572

Readme

stylelint-config-sonarqube

A Stylelint config that attempts to map sonar css rules to stylelint rules.

Mapping

This mapping has been used to come to the correct styleint rules to use.

The following Sonar CSS rules are covered

  • "!important" annotation should not be used
  • CSS should be written in lower case
  • Duplicated properties should be removed
  • Each declaration should end with a semicolon
  • Empty declarations should be removed
  • Empty rules should be removed
  • Empty stylesheets should be removed
  • Experimental @-rules should not be used
  • Experimental identifiers should not be used
  • Experimental properties should not be used
  • Files should contain an empty new line at the end
  • Leading zeros should be removed
  • Lines should not be too long
  • Lines should not end with trailing whitespaces
  • Over-specified selectors should be simplified
  • Protocol-relative URL should not be used
  • Shorthand properties should be used whenever possible
  • Single quotes should be used instead of double quotes for strings
  • Source code should comply with formatting standards
  • There should be one single declaration per line
  • Trailing zeros for numeric values should be removed
  • Units for zero length values should be removed
  • Unknown @-rules should be removed
  • Unknown properties should be removed
  • Unknown pseudo-elements and pseudo-classes should be removed
  • Unknown type selectors should be removed
  • URL should be quoted

If you are using SCSS you might want to add the following rules manually:

// Unknown @-rules should be removed
"at-rule-no-unknown": null,
"scss/at-rule-no-unknown": true,

// Rulesets should not be nested too deeply
"max-nesting-depth": 3

How to use

Install the npm module:

yarn add stylelint-config-sonarqube --dev

or

npm install stylelint-config-sonarqube --save-dev

Extend the Stylelint ruleset by adding this to your .stylelintrc.js:

module.exports = {
  extends: ["stylelint-config-sonarqube"]
};

You can extend it with your own rules and plugins.