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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@csssr/linters

v0.1.1

Published

CSSSR's linting configs for Prettier and ESLint

Readme

CSSSR's linting configs for Prettier and ESLint.

Documentation

Installation

First install @csssr/linters itself:

npm i -D @csssr/linters

yarn add -D @csssr/linters

Then install peer dependencies (Prettier, ESLint and its plugins):

npx install-peerdeps -D @csssr/linters

Prettier configuration

You may use your own Prettier config or use predefined one:

// File: .prettierrc.js
module.exports = {
  ...require('@csssr/linters/prettier.config'),
}

ESLint configuration

There are several predefined configurations, which you may include in your project based on your project needs:

  • eslint/base - basic JavaScript rules including Prettier rule
  • exlint/react - React and JSX rules
  • eslint/typescript - TS-specific rules

Linting Babel project

Install @babel/eslint-parser and add it as a parser to ESLint config:

// File: .eslintrc.js
module.exports = {
  parser: "@babel/eslint-parser",
  extends: [
    require.resolve('@csssr/linters/eslint/base'),
    require.resolve('@csssr/linters/eslint/react'),
  ],
}

Linting TypeScript project

// File: .eslintrc.js
module.exports = {
  extends: [
    require.resolve('@csssr/linters/eslint/base'),
    require.resolve('@csssr/linters/eslint/react'),
    require.resolve('@csssr/linters/eslint/typescript'),
  ],
}

tsconfig.json from root of the project will be used for gathering type info for some rules. If your TS config is located elsewhere, configure its path in parserOptions.project field of ESLint config.

Only files specified in include section of tsconfig.json will be linted. Because of that configs located in the root folder (.eslintrc.js, .prettierrc.js, etc.) will not be linted but can still be formatted with Prettier.

Customization

Feel free to add new plugins and rules and disable existing rules which are not suitable for your project's needs:

// File: .eslintrc.js
module.exports = {
  extends: [
    require.resolve('@csssr/linters/eslint/base'),
    require.resolve('@csssr/linters/eslint/react'),
    require.resolve('@csssr/linters/eslint/typescript'),
  ],
  plugins: ['todo-plz'],
  rules: {
    // Disabling for Next project
    'jsx-a11y/anchor-is-valid': 'off',
    
    // New rule for linting todos
    'todo-plz/ticket-ref': [
      'error',
      {
        pattern: 'PROJ-[0-9]+',
        terms: ['TODO', 'todo'],
      },
    ],
  },
  overrides: [
    {
      // Storybook's CSF requires usage of default exports
      files: ['./src/**/index.stories.tsx'],
      rules: {
        'import/no-default-export': ['off'],
      },
    },
  ],
}

You can find more recommendations for manual configuration here.

Contributing