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

eslint-plugin-react-import

v1.1.0

Published

ESLint plugin to ensure consistent react imports

Downloads

190

Readme

eslint-plugin-react-import

CI Code style: prettier npm version issues

ESLint plugin to ensure consistent react imports

[!WARNING] This plugin supports eslint 8 but do not expose legacy configs. See the guide below use this plugin with legacy config

Rules

💼 Configurations enabled in.
✅ Set in the recommended configuration.
🔧 Automatically fixable by the --fix CLI option.

| Name              | Description | 💼 | 🔧 | | :--------------------------------------------------- | :-------------------------------------------------------------------------------------------------- | :- | :- | | consistent-syntax | Enforces React import style across your code. Can be customized to use default or namespace import. | ✅ | 🔧 |

Installation

npm i --save-dev eslint eslint-plugin-react-import
yarn add --dev eslint eslint-plugin-react-import
pnpm add --save-dev eslint eslint-plugin-react-import

Configuration

[!TIP] For a working example check tests/fixtures folders

Javascript

// eslint.config.js
import eslintPluginReactImport from "eslint-plugin-react-import";
export default [
  // other configs
  // ...
  eslintPluginReactImport.configs.recommended,
];

Typescript

[!NOTE] In order to replace all type occurrences typescript parser should be used

// eslint.config.js
import eslintPluginReactImport from "eslint-plugin-react-import";
import typescriptEslintParser from "@typescript-eslint/parser";

export default [
  // other configs
  // ...
  {
    ...eslintPluginReactImport.configs.recommended,
    languageOptions: {
      ...eslintPluginReactImport.configs.recommended.languageOptions,
      parser: typescriptEslintParser,
    },
  },
];

Configuration (legacy eslintrc)

For legacy config there is no exported config. Since this plugin include one rule you just need to add the plugin name to plugins list and configure the rules:

module.exports = {
  root: true,
  plugins: [
    // Other plugins...
    "react-import"
    ],
  // Remember to change parser if you are using ts
  parser: "@typescript-eslint/parser",
  parserOptions: {
    // ...
  },
  rules: {
    // Configure the rule
    "react-import/consistent-syntax": ["error", "namespace"],
  },
};