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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@salesforce-ux/sds-linter

v0.0.2

Published

SDS Linter with both stylelint and eslint together

Downloads

8

Readme

SDS Linter

Features

  • Component Linting: The utility supports linting for two types of Salesforce Lightning components:

    • LWC and Aura components. LWC Components (.html): Linting is applied to Lightning Web Components.
    • Aura Components (.cmp): Linting is applied to Aura Components.
  • Stylelint for CSS FilesStylelint rules are applied to .css files associated with the components. This ensures consistent styling practices are followed throughout the project.

Installation

To install the SDS Linter Utility in your project, you can use npm:

npm install --save-dev sds-linter

Usage

After installing the package, you need to add a few commands to your package.json to allow running the commands needed for linting.

You need to add the below in "scripts" item in package.json

"lint:styles": "stylelint './**/*.css' --config=.stylelintrc.yml",
"lint:components": "eslint '**/*.{html,cmp}' --ext .html,.cmp --config=.eslintrc.yml",
"lint": "npm run lint:components; npm run lint:styles",
"fix": "stylelint '**/*.css' -c .stylelintrc.yml --fix ",
"report": "node node_modules/@salesforce-ux/stylelint-sds/build/report.js force-app/ -c .stylelintrc.yml",
"setup-lint": "node ./node_modules/@salesforce-ux/sds-linter/build/setup.js"

once the above scripts are added. You can setup the configuration by running

npm run setup-lint

which will inturn create .eslintrc.yml & .stylelintrc.yml in the root folder.

NOTE: If the project root already containing .eslintrc.yml & .stylelintrc.yml, we don't overwrite those files and the use needs to merge those files manually. You can find the configuration files in this repostory in the root folder.

Command-Line Interface (CLI)

  • To lint all components and styles in your project:

    npx run lint
  • To auto-fix some of the most confident fixes automatically.

    npx run fix
  • To run a report in .sarif format

    npx run report

Contribution

We welcome contributions to improve this utility. If you have any suggestions, bug reports, or want to contribute code, please open an issue or pull request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

For any questions or issues, feel free to reach out to the maintainers or open an issue in the repository.