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

@vtex/shoreline-stylelint

v1.0.74

Published

A configuration of [Stylelint](https://stylelint.io/) rules to help with the Shoreline adoption.

Downloads

443

Readme

Shoreline Stylelint

A configuration of Stylelint rules to help with the Shoreline adoption.

How to run?

All files:

pnpm stylelint **/*.css

Specific file:

pnpm run stylelint src/example.css

Fix:

pnpm stylelint **/*.css --fix

Development

Add new rules

  1. Refer to the Writing rules guide of the Stylelint documentation

Build custom rules

  1. Refer to the Writing plugins guide of the Stylelint documentation
  2. Create your rule in the /src/plugins directory
  3. Validate your plugin with tests (reference sibling plugins for examples)

Useful references:

  1. PostCSS API: It is useful when writing a new plugin.
  2. jest-preset-stylelint: Use this documentation when writing tests.
  3. stylelint-prettier

Setup new rule or plugin

You must set the new rule or plugin on the Stylelint configuration file

Rules

no-px-values

This rule prevents your CSS properties from having a px value defined.

/* Don't 🚫 */
margin: 4px;
padding-bottom: 8px;
padding-top: 8px;
height: 24px;

/* Do ✅ */
margin: 0.25rem;
padding-bottom: 0.5rem;
padding-top: 0.5rem;
height: 1.5rem;

Using the --fix command will convert the px values to rem.

no-text-property

/* Don't 🚫 */
text: var(--sl-text-caption-2);

/* Do ✅ */
font: var(--sl-text-caption-2-font);
letter-spacing: var(--sl-text-caption-2-letter-spacing);

Using the --fix command will split the text property into font and letter-spacing.