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

eslint-plugin-nice-styled-rules

v1.0.2

Published

An ESLint plugin that lets you control the usage rules for styled components in your project.

Readme

eslint-plugin-nice-styled-rules

An ESLint plugin that lets you control the usage rules for styled components in your project. This rule allows you to add flexible restrictions on the number of style imports and enforce a specific naming convention.

Installation

Install the plugin as a dev dependency: bash npm install --save-dev eslint-plugin-nice-styled-rules or bash yarn add --dev eslint-plugin-nice-styled-rules

Additional required dependencies

To ensure correct resolution of TypeScript imports (including styled component files), make sure you have also installed the following packages: bash npm install --save-dev eslint-plugin-import eslint-import-resolver-typescript And in your ESLint configuration (e.g., .eslintrc.js), you need to add the following settings:

js
module.exports = {
  // ...
  settings: {
    'import/resolver': {
      typescript: {
        project: 'tsconfig.json', // Make sure this path is correct for your project
      },
      node: {
        extensions: ['.js', '.ts', '.tsx', '.d.ts'],
      },
    },
  },
  // ...
};

This ensures that ESLint (and the eslint-plugin-import) can properly resolve .ts/.tsx files and any paths you’ve set in your tsconfig.json.

Configuration

  1. Add the "nice-styled-rules" plugin to the “plugins” section of your ESLint configuration file (usually .eslintrc.js or .eslintrc):
js
module.exports = {
  // ...
  plugins: [
    'nice-styled-rules'
  ],
  // ...
};
  1. Add the actual rule to the “rules” section:
js
module.exports = {
  // ...
  rules: {
    'nice-styled-rules/no-multiple-styled-imports': 'warn',
    // or 'error' if you want ESLint to throw an error instead of a warning
  },
};

Rule Description

no-multiple-styled-imports

This rule prohibits using more than one import of styled components in a component file. In addition, the imported file must include the full name of the current component with the substring “Styled”. Also, the imported styles file must be located in the same directory as the component that uses the styles. • For example, if your component is named “ButtonHello,” the correct style file name to import would be “ButtonHelloStyled” (or “ButtonHelloStyled.ts,” “ButtonHelloStyled.js,” etc.).• If the component file contains other imports ending with “Styled” that do not match the component name, the rule will issue a warning (“warn”) or an error (“error”), depending on your configuration. This rule simplifies project navigation and helps maintain a uniform structure for importing styled components.