Convert Figma logo to code with AI

jsx-eslint logoeslint-plugin-react

React-specific linting rules for ESLint

9,131
2,764
9,131
326

Top Related Projects

233,534

The library for web and native user interfaces.

146,335

JavaScript Style Guide

React-specific linting rules for ESLint

49,809

Prettier is an opinionated code formatter.

:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript

25,435

Find and fix problems in your JavaScript code.

Quick Overview

ESLint-plugin-react is a popular ESLint plugin specifically designed for React applications. It provides a comprehensive set of rules to enforce best practices, catch common mistakes, and maintain consistency in React codebases.

Pros

  • Extensive rule set covering various aspects of React development
  • Highly configurable, allowing teams to customize rules based on project needs
  • Regular updates to support new React features and best practices
  • Integration with popular IDEs and text editors for real-time linting

Cons

  • Can be overwhelming for beginners due to the large number of rules
  • Some rules may conflict with personal or team preferences, requiring careful configuration
  • Occasional false positives, especially with complex or unconventional code patterns
  • Performance impact on large codebases when using many rules simultaneously

Code Examples

  1. Enforcing prop types:
// Bad
function MyComponent({ name }) {
  return <div>{name}</div>;
}

// Good
import PropTypes from 'prop-types';

function MyComponent({ name }) {
  return <div>{name}</div>;
}

MyComponent.propTypes = {
  name: PropTypes.string.isRequired,
};
  1. Enforcing JSX closing bracket location:
// Bad
const MyComponent = () => (
  <div>
    <span>Content</span>
  </div>
);

// Good
const MyComponent = () => (
  <div>
    <span>Content</span>
  </div>
);
  1. Preventing usage of deprecated methods:
// Bad
class MyComponent extends React.Component {
  componentWillMount() {
    // Deprecated lifecycle method
  }
}

// Good
class MyComponent extends React.Component {
  componentDidMount() {
    // Use this instead
  }
}

Getting Started

  1. Install the plugin:
npm install eslint eslint-plugin-react --save-dev
  1. Add the plugin to your ESLint configuration file (e.g., .eslintrc.js):
module.exports = {
  plugins: ['react'],
  extends: [
    'eslint:recommended',
    'plugin:react/recommended'
  ],
  rules: {
    // Add custom rules here
  }
};
  1. Run ESLint:
npx eslint .

Competitor Comparisons

233,534

The library for web and native user interfaces.

Pros of React

  • Core library for building user interfaces, offering a complete ecosystem
  • Extensive community support and resources
  • Regular updates and improvements from Facebook's dedicated team

Cons of React

  • Larger package size and potentially higher resource usage
  • Steeper learning curve for beginners
  • Requires additional tools and libraries for a complete development environment

Code Comparison

React:

import React from 'react';

function MyComponent() {
  return <div>Hello, React!</div>;
}

eslint-plugin-react:

module.exports = {
  plugins: ['react'],
  rules: {
    'react/jsx-uses-react': 'error',
    'react/jsx-uses-vars': 'error',
  },
};

Key Differences

  • React is a JavaScript library for building user interfaces, while eslint-plugin-react is an ESLint plugin for React-specific linting rules
  • React focuses on component-based architecture and efficient rendering, while eslint-plugin-react helps maintain code quality and best practices
  • React is essential for developing React applications, whereas eslint-plugin-react is an optional tool for improving code consistency and catching common errors

Use Cases

  • Use React when building interactive user interfaces and single-page applications
  • Use eslint-plugin-react alongside React development to enforce coding standards and catch potential issues early in the development process
146,335

JavaScript Style Guide

Pros of javascript

  • Comprehensive style guide covering various JavaScript aspects beyond React
  • Widely adopted industry standard with extensive community support
  • Includes guidelines for ES6+ features and modern JavaScript practices

Cons of javascript

  • May be overly opinionated for some developers or projects
  • Requires additional configuration for React-specific linting rules
  • Can be overwhelming for beginners due to its extensive nature

Code Comparison

eslint-plugin-react:

// .eslintrc.js
module.exports = {
  plugins: ['react'],
  extends: ['eslint:recommended', 'plugin:react/recommended'],
  // ...
}

javascript:

// .eslintrc.js
module.exports = {
  extends: ['airbnb', 'airbnb/hooks'],
  // ...
}

Summary

eslint-plugin-react focuses specifically on React-related linting rules, while javascript provides a comprehensive JavaScript style guide that includes React best practices. eslint-plugin-react offers more flexibility and customization for React projects, whereas javascript provides a complete set of rules for JavaScript development in general. The choice between the two depends on project requirements, team preferences, and the desired level of customization.

React-specific linting rules for ESLint

Pros of eslint-plugin-react

  • More comprehensive set of rules specifically tailored for React development
  • Larger community and more frequent updates
  • Better integration with popular React-based frameworks and tools

Cons of eslint-plugin-react

  • Potentially more complex configuration due to the extensive rule set
  • May require more time to set up and customize for specific project needs
  • Higher likelihood of false positives in certain edge cases

Code Comparison

eslint-plugin-react:

{
  "plugins": ["react"],
  "extends": ["eslint:recommended", "plugin:react/recommended"],
  "rules": {
    "react/jsx-uses-react": "error",
    "react/jsx-uses-vars": "error"
  }
}

Both repositories are actually the same project, as jsx-eslint/eslint-plugin-react is the current location of the eslint-plugin-react project. The comparison above is based on the features and characteristics of eslint-plugin-react itself, as there isn't a separate project to compare it against in this case.

The eslint-plugin-react project provides a comprehensive set of ESLint rules specifically designed for React development. It offers extensive customization options and is widely adopted in the React community. The configuration example shows how to include the plugin and extend its recommended ruleset in an ESLint configuration file.

49,809

Prettier is an opinionated code formatter.

Pros of Prettier

  • Opinionated and requires minimal configuration
  • Supports multiple languages beyond JavaScript and React
  • Automatically formats code, saving time and reducing debates over style

Cons of Prettier

  • Less flexible for custom formatting rules
  • May conflict with existing ESLint rules
  • Limited to code formatting, doesn't catch potential errors or best practices

Code Comparison

eslint-plugin-react:

import React from 'react';

const Component = ({ prop1, prop2 }) => (
  <div className="example">
    {prop1 && <span>{prop2}</span>}
  </div>
);

Prettier:

import React from "react";

const Component = ({ prop1, prop2 }) => (
  <div className="example">{prop1 && <span>{prop2}</span>}</div>
);

Key Differences

  • eslint-plugin-react focuses on React-specific linting rules and best practices
  • Prettier is a code formatter that works across multiple languages
  • eslint-plugin-react allows for more customization of rules
  • Prettier enforces a consistent style with minimal configuration

Use Cases

  • Use eslint-plugin-react for catching React-specific issues and enforcing best practices
  • Use Prettier for consistent code formatting across your project
  • Many developers use both tools in combination for comprehensive code quality management

:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript

Pros of typescript-eslint

  • Comprehensive TypeScript support with specialized rules and parser
  • Seamless integration with the TypeScript compiler for enhanced type checking
  • Regular updates and active maintenance for the latest TypeScript features

Cons of typescript-eslint

  • Steeper learning curve for developers new to TypeScript
  • Potentially slower linting process due to additional type checking
  • May require more configuration for optimal use in mixed JavaScript/TypeScript projects

Code Comparison

eslint-plugin-react:

// .eslintrc.js
module.exports = {
  plugins: ['react'],
  rules: {
    'react/jsx-uses-react': 'error',
    'react/jsx-uses-vars': 'error',
  },
};

typescript-eslint:

// .eslintrc.js
module.exports = {
  parser: '@typescript-eslint/parser',
  plugins: ['@typescript-eslint'],
  extends: ['plugin:@typescript-eslint/recommended'],
  rules: {
    '@typescript-eslint/explicit-function-return-type': 'error',
  },
};

Both eslint-plugin-react and typescript-eslint are valuable tools for linting React projects. eslint-plugin-react focuses specifically on React-related rules and best practices, while typescript-eslint provides comprehensive TypeScript support with additional type-aware rules. The choice between them depends on whether your project uses TypeScript and the level of type checking you require.

25,435

Find and fix problems in your JavaScript code.

Pros of eslint

  • More comprehensive linting capabilities, covering a wide range of JavaScript and ECMAScript features
  • Highly customizable with a vast ecosystem of plugins and configurations
  • Supports multiple environments beyond React, making it suitable for various JavaScript projects

Cons of eslint

  • Requires additional configuration for React-specific linting rules
  • May have a steeper learning curve for React developers who only need React-specific rules
  • Can be more resource-intensive due to its broader scope

Code Comparison

eslint:

module.exports = {
  "env": {
    "browser": true,
    "es2021": true
  },
  "extends": "eslint:recommended",
  "rules": {
    // General JavaScript rules
  }
}

eslint-plugin-react:

module.exports = {
  "plugins": [
    "react"
  ],
  "extends": [
    "eslint:recommended",
    "plugin:react/recommended"
  ],
  "rules": {
    // React-specific rules
  }
}

The eslint configuration focuses on general JavaScript linting, while eslint-plugin-react specifically targets React development with dedicated rules and extensions.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

eslint-plugin-react Version Badge

===================

github actions Maintenance Status NPM version Tidelift

React specific linting rules for eslint

Installation

npm install eslint eslint-plugin-react --save-dev

It is also possible to install ESLint globally rather than locally (using npm install -g eslint). However, this is not recommended, and any plugins or shareable configs that you use must be installed locally in either case.

Configuration (legacy: .eslintrc*)

Use our preset to get reasonable defaults:

  "extends": [
    "eslint:recommended",
    "plugin:react/recommended"
  ]

If you are using the new JSX transform from React 17, extend react/jsx-runtime in your eslint config (add "plugin:react/jsx-runtime" to "extends") to disable the relevant rules.

You should also specify settings that will be shared across all the plugin rules. (More about eslint shared settings)

{
  "settings": {
    "react": {
      "createClass": "createReactClass", // Regex for Component Factory to use,
                                         // default to "createReactClass"
      "pragma": "React",  // Pragma to use, default to "React"
      "fragment": "Fragment",  // Fragment to use (may be a property of <pragma>), default to "Fragment"
      "version": "detect", // React version. "detect" automatically picks the version you have installed.
                           // You can also use `16.0`, `16.3`, etc, if you want to override the detected value.
                           // Defaults to the "defaultVersion" setting and warns if missing, and to "detect" in the future
      "defaultVersion": "", // Default React version to use when the version you have installed cannot be detected.
                            // If not provided, defaults to the latest React version.
      "flowVersion": "0.53" // Flow version
    },
    "propWrapperFunctions": [
        // The names of any function used to wrap propTypes, e.g. `forbidExtraProps`. If this isn't set, any propTypes wrapped in a function will be skipped.
        "forbidExtraProps",
        {"property": "freeze", "object": "Object"},
        {"property": "myFavoriteWrapper"},
        // for rules that check exact prop wrappers
        {"property": "forbidExtraProps", "exact": true}
    ],
    "componentWrapperFunctions": [
        // The name of any function used to wrap components, e.g. Mobx `observer` function. If this isn't set, components wrapped by these functions will be skipped.
        "observer", // `property`
        {"property": "styled"}, // `object` is optional
        {"property": "observer", "object": "Mobx"},
        {"property": "observer", "object": "<pragma>"} // sets `object` to whatever value `settings.react.pragma` is set to
    ],
    "formComponents": [
      // Components used as alternatives to <form> for forms, eg. <Form endpoint={ url } />
      "CustomForm",
      {"name": "SimpleForm", "formAttribute": "endpoint"},
      {"name": "Form", "formAttribute": ["registerEndpoint", "loginEndpoint"]}, // allows specifying multiple properties if necessary
    ],
    "linkComponents": [
      // Components used as alternatives to <a> for linking, eg. <Link to={ url } />
      "Hyperlink",
      {"name": "MyLink", "linkAttribute": "to"},
      {"name": "Link", "linkAttribute": ["to", "href"]}, // allows specifying multiple properties if necessary
    ]
  }
}

If you do not use a preset you will need to specify individual rules and add extra configuration.

Add "react" to the plugins section.

{
  "plugins": [
    "react"
  ]
}

Enable JSX support.

With eslint 2+

{
  "parserOptions": {
    "ecmaFeatures": {
      "jsx": true
    }
  }
}

Enable the rules that you would like to use.

  "rules": {
    "react/jsx-uses-react": "error",
    "react/jsx-uses-vars": "error",
  }

Shareable configs

Recommended

This plugin exports a recommended configuration that enforces React good practices.

To enable this configuration use the extends property in your .eslintrc config file:

{
  "extends": ["eslint:recommended", "plugin:react/recommended"]
}

See eslint documentation for more information about extending configuration files.

All

This plugin also exports an all configuration that includes every available rule. This pairs well with the eslint:all rule.

{
  "plugins": [
    "react"
  ],
  "extends": ["eslint:all", "plugin:react/all"]
}

Note: These configurations will import eslint-plugin-react and enable JSX in parser options.

Configuration (new: eslint.config.js)

From v8.21.0, eslint announced a new config system. In the new system, .eslintrc* is no longer used. eslint.config.js would be the default config file name. In eslint v8, the legacy system (.eslintrc*) would still be supported, while in eslint v9, only the new system would be supported.

And from v8.23.0, eslint CLI starts to look up eslint.config.js. So, if your eslint is >=8.23.0, you're 100% ready to use the new config system.

You might want to check out the official blog posts,

and the official docs.

Plugin

The default export of eslint-plugin-react is a plugin object.

const react = require('eslint-plugin-react');
const globals = require('globals');

module.exports = [
  …
  {
    files: ['**/*.{js,jsx,mjs,cjs,ts,tsx}'],
    plugins: {
      react,
    },
    languageOptions: {
      parserOptions: {
        ecmaFeatures: {
          jsx: true,
        },
      },
      globals: {
        ...globals.browser,
      },
    },
    rules: {
      // ... any rules you want
      'react/jsx-uses-react': 'error',
      'react/jsx-uses-vars': 'error',
     },
    // ... others are omitted for brevity
  },
  …
];

Configuring shared settings

Refer to the official docs.

The schema of the settings.react object would be identical to that of what's already described above in the legacy config section.

Flat Configs

This plugin exports 3 flat configs:

  • flat.all
  • flat.recommended
  • flat['jsx-runtime']

The flat configs are available via the root plugin import. They will configure the plugin under the react/ namespace and enable JSX in languageOptions.parserOptions.

const reactPlugin = require('eslint-plugin-react');

module.exports = [
  …
  reactPlugin.configs.flat.recommended, // This is not a plugin object, but a shareable config object
  reactPlugin.configs.flat['jsx-runtime'], // Add this if you are using React 17+
  …
];

You can of course add/override some properties.

Note: Our shareable configs does not preconfigure files or languageOptions.globals. For most of the cases, you probably want to configure some properties by yourself.

const reactPlugin = require('eslint-plugin-react');
const globals = require('globals');

module.exports = [
  …
  {
    files: ['**/*.{js,mjs,cjs,jsx,mjsx,ts,tsx,mtsx}'],
    ...reactPlugin.configs.flat.recommended,
    languageOptions: {
      ...reactPlugin.configs.flat.recommended.languageOptions,
      globals: {
        ...globals.serviceworker,
        ...globals.browser,
      },
    },
  },
  …
];

The above example is same as the example below, as the new config system is based on chaining.

const reactPlugin = require('eslint-plugin-react');
const globals = require('globals');

module.exports = [
  …
  {
    files: ['**/*.{js,mjs,cjs,jsx,mjsx,ts,tsx,mtsx}'],
    ...reactPlugin.configs.flat.recommended,
  },
  {
    files: ['**/*.{js,mjs,cjs,jsx,mjsx,ts,tsx,mtsx}'],
    languageOptions: {
      globals: {
        ...globals.serviceworker,
        ...globals.browser,
      },
    },
  },
  …
];

List of supported rules

💼 Configurations enabled in.
🚫 Configurations disabled in.
🏃 Set in the jsx-runtime configuration.
☑️ Set in the recommended configuration.
🔧 Automatically fixable by the --fix CLI option.
💡 Manually fixable by editor suggestions.
❌ Deprecated.

Name                                 Description💼🚫🔧💡❌
boolean-prop-namingEnforces consistent naming for boolean props
button-has-typeDisallow usage of button elements without an explicit type attribute
checked-requires-onchange-or-readonlyEnforce using onChange or readonly attribute when checked is used
default-props-match-prop-typesEnforce all defaultProps have a corresponding non-required PropType
destructuring-assignmentEnforce consistent usage of destructuring assignment of props, state, and context🔧
display-nameDisallow missing displayName in a React component definition☑️
forbid-component-propsDisallow certain props on components
forbid-dom-propsDisallow certain props on DOM Nodes
forbid-elementsDisallow certain elements
forbid-foreign-prop-typesDisallow using another component's propTypes
forbid-prop-typesDisallow certain propTypes
forward-ref-uses-refRequire all forwardRef components include a ref parameter💡
function-component-definitionEnforce a specific function type for function components🔧
hook-use-stateEnsure destructuring and symmetric naming of useState hook value and setter variables💡
iframe-missing-sandboxEnforce sandbox attribute on iframe elements
jsx-boolean-valueEnforce boolean attributes notation in JSX🔧
jsx-child-element-spacingEnforce or disallow spaces inside of curly braces in JSX attributes and expressions
jsx-closing-bracket-locationEnforce closing bracket location in JSX🔧
jsx-closing-tag-locationEnforce closing tag location for multiline JSX🔧
jsx-curly-brace-presenceDisallow unnecessary JSX expressions when literals alone are sufficient or enforce JSX expressions on literals in JSX children or attributes🔧
jsx-curly-newlineEnforce consistent linebreaks in curly braces in JSX attributes and expressions🔧
jsx-curly-spacingEnforce or disallow spaces inside of curly braces in JSX attributes and expressions🔧
jsx-equals-spacingEnforce or disallow spaces around equal signs in JSX attributes🔧
jsx-filename-extensionDisallow file extensions that may contain JSX
jsx-first-prop-new-lineEnforce proper position of the first property in JSX🔧
jsx-fragmentsEnforce shorthand or standard form for React fragments🔧
jsx-handler-namesEnforce event handler naming conventions in JSX
jsx-indentEnforce JSX indentation🔧
jsx-indent-propsEnforce props indentation in JSX🔧
jsx-keyDisallow missing key props in iterators/collection literals☑️
jsx-max-depthEnforce JSX maximum depth
jsx-max-props-per-lineEnforce maximum of props on a single line in JSX🔧
jsx-newlineRequire or prevent a new line after jsx elements and expressions.🔧
jsx-no-bindDisallow .bind() or arrow functions in JSX props
jsx-no-comment-textnodesDisallow comments from being inserted as text nodes☑️
jsx-no-constructed-context-valuesDisallows JSX context provider values from taking values that will cause needless rerenders
jsx-no-duplicate-propsDisallow duplicate properties in JSX☑️
jsx-no-leaked-renderDisallow problematic leaked values from being rendered🔧
jsx-no-literalsDisallow usage of string literals in JSX
jsx-no-script-urlDisallow usage of javascript: URLs
jsx-no-target-blankDisallow target="_blank" attribute without rel="noreferrer"☑️🔧
jsx-no-undefDisallow undeclared variables in JSX☑️
jsx-no-useless-fragmentDisallow unnecessary fragments🔧
jsx-one-expression-per-lineRequire one JSX element per line🔧
jsx-pascal-caseEnforce PascalCase for user-defined JSX components
jsx-props-no-multi-spacesDisallow multiple spaces between inline JSX props🔧
jsx-props-no-spread-multiDisallow JSX prop spreading the same identifier multiple times
jsx-props-no-spreadingDisallow JSX prop spreading
jsx-sort-default-propsEnforce defaultProps declarations alphabetical sorting❌
jsx-sort-propsEnforce props alphabetical sorting🔧
jsx-space-before-closingEnforce spacing before closing bracket in JSX🔧❌
jsx-tag-spacingEnforce whitespace in and around the JSX opening and closing brackets🔧
jsx-uses-reactDisallow React to be incorrectly marked as unused☑️🏃
jsx-uses-varsDisallow variables used in JSX to be incorrectly marked as unused☑️
jsx-wrap-multilinesDisallow missing parentheses around multiline JSX🔧
no-access-state-in-setstateDisallow when this.state is accessed within setState
no-adjacent-inline-elementsDisallow adjacent inline elements not separated by whitespace.
no-array-index-keyDisallow usage of Array index in keys
no-arrow-function-lifecycleLifecycle methods should be methods on the prototype, not class fields🔧
no-children-propDisallow passing of children as props☑️
no-dangerDisallow usage of dangerous JSX properties
no-danger-with-childrenDisallow when a DOM element is using both children and dangerouslySetInnerHTML☑️
no-deprecatedDisallow usage of deprecated methods☑️
no-did-mount-set-stateDisallow usage of setState in componentDidMount
no-did-update-set-stateDisallow usage of setState in componentDidUpdate
no-direct-mutation-stateDisallow direct mutation of this.state☑️
no-find-dom-nodeDisallow usage of findDOMNode☑️
no-invalid-html-attributeDisallow usage of invalid attributes💡
no-is-mountedDisallow usage of isMounted☑️
no-multi-compDisallow multiple component definition per file
no-namespaceEnforce that namespaces are not used in React elements
no-object-type-as-default-propDisallow usage of referential-type variables as default param in functional component
no-redundant-should-component-updateDisallow usage of shouldComponentUpdate when extending React.PureComponent
no-render-return-valueDisallow usage of the return value of ReactDOM.render☑️
no-set-stateDisallow usage of setState
no-string-refsDisallow using string references☑️
no-this-in-sfcDisallow this from being used in stateless functional components
no-typosDisallow common typos
no-unescaped-entitiesDisallow unescaped HTML entities from appearing in markup☑️💡
no-unknown-propertyDisallow usage of unknown DOM property☑️🔧
no-unsafeDisallow usage of unsafe lifecycle methods☑️
no-unstable-nested-componentsDisallow creating unstable components inside components
no-unused-class-component-methodsDisallow declaring unused methods of component class
no-unused-prop-typesDisallow definitions of unused propTypes
no-unused-stateDisallow definitions of unused state
no-will-update-set-stateDisallow usage of setState in componentWillUpdate
prefer-es6-classEnforce ES5 or ES6 class for React Components
prefer-exact-propsPrefer exact proptype definitions
prefer-read-only-propsEnforce that props are read-only🔧
prefer-stateless-functionEnforce stateless components to be written as a pure function
prop-typesDisallow missing props validation in a React component definition☑️
react-in-jsx-scopeDisallow missing React when using JSX☑️🏃
require-default-propsEnforce a defaultProps definition for every prop that is not a required prop
require-optimizationEnforce React components to have a shouldComponentUpdate method
require-render-returnEnforce ES5 or ES6 class for returning value in render function☑️
self-closing-compDisallow extra closing tags for components without children🔧
sort-compEnforce component methods order
sort-default-propsEnforce defaultProps declarations alphabetical sorting
sort-prop-typesEnforce propTypes declarations alphabetical sorting🔧
state-in-constructorEnforce class component state initialization style
static-property-placementEnforces where React component static properties should be positioned.
style-prop-objectEnforce style prop value is an object
void-dom-elements-no-childrenDisallow void DOM elements (e.g. <img />, <br />) from receiving children

Other useful plugins

License

eslint-plugin-react is licensed under the MIT License.

NPM DownloadsLast 30 Days