Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
eslint-plugin-react-prefer-function-component
Advanced tools
ESLint plugin that prevents the use of JSX class components
An ESLint plugin that prevents the use of React class components.
An ESLint plugin that prevents the use of React class components. While this plugin specifically calls out React, it will work with Preact, Inferno, or other JSX libraries.
Since the addition of hooks, it has been possible to write stateful React components using only functions.
Leaving the choice between class or function components up to the community is great, but generally within a codebase I want consistency: either we're writing class components and HoCs or we're using function components and hooks. Straddling the two adds unnecessary hurdles for sharing reusable logic.
By default, class components that use componentDidCatch
are enabled because there is currently no hook alternative for React. This option is configurable via allowComponentDidCatch
.
This rule is intended to complement the eslint-plugin-react rule set.
What about
ErrorBoundary
class components? Does this lint rule support those?
Yes it does. Error Boundaries are implemented by defining componentDidCatch
. Because there is currently no hook equivalent, class components that implement componentDidCatch
are allowed by default.
This option is configurable.
What about eslint-plugin-react/prefer-stateless-function?
eslint-plugin-react/prefer-stateless-function
allows class components that implement any methods or properties other than render
. This rule is stricter and prevents the use of any class components. This open issue explains the limitations of prefer-stateless-function
and the motivations for this plugin.
Why didn't you contribute this rule to https://github.com/yannickcr/eslint-plugin-react?
I'm discussing this in an open issue and pull request on eslint-plugin-react
. At this time, the maintainer of eslint-plugin-react
is unconvinced that function component enforcement should be a lint rule. If you would like to see this rule added to eslint-plugin-react
, please join the discussion on the issue or pull request.
$ npm install eslint eslint-plugin-react-prefer-function-component --save-dev
eslint.config.js
:import eslint from "@eslint/js";
import reactRecommended from "eslint-plugin-react/configs/recommended.js";
import preferFC from "eslint-plugin-react-prefer-function-component/config";
export default [
{ files: ["**/*.{js,jsx}"] },
eslint.configs.recommended,
reactRecommended,
preferFC.configs.recommended,
];
.eslintrc
configuration:
module.exports = {
extends: ["plugin:react-prefer-function-component/recommended"],
};
Or customize:
module.exports = {
plugins: ["react-prefer-function-component"],
rules: {
"react-prefer-function-component/react-prefer-function-component": [
"error",
{ allowComponentDidCatch: false },
],
},
};
For more configuration examples, take a look at the examples directory.
This rule will flag any React class components that don't use componentDidCatch
.
Examples of incorrect code for this rule:
import { Component } from "react";
class Foo extends Component {
render() {
return <div>{this.props.foo}</div>;
}
}
Examples of correct code for this rule:
function Foo(props) {
return <div>{props.foo}</div>;
}
const Foo = ({ foo }) => <div>{foo}</div>;
...
"prefer-function-component": [<enabled>, { "allowComponentDidCatch": <allowComponentDidCatch>, "allowJsxUtilityClass": <allowJsxUtilityClass> }]
...
enabled
: for enabling the rule. 0=off, 1=warn, 2=error. Defaults to 0.allowComponentDidCatch
: optional boolean. set to false
if you want to also flag class components that use componentDidCatch
(defaults to true
).allowJsxUtilityClass
: optional boolean. set to true
if you want to allow classes that contain JSX but aren't class components (defaults to false
).allowComponentDidCatch
When true
(the default) the rule will ignore components that use componentDidCatch
Examples of correct code for this rule:
import { Component } from "react";
class Foo extends Component {
componentDidCatch(error, errorInfo) {
logErrorToMyService(error, errorInfo);
}
render() {
return <div>{this.props.foo}</div>;
}
}
When false
the rule will also flag components that use componentDidCatch
Examples of incorrect code for this rule:
import { Component } from "react";
class Foo extends Component {
componentDidCatch(error, errorInfo) {
logErrorToMyService(error, errorInfo);
}
render() {
return <div>{this.props.foo}</div>;
}
}
allowJsxUtilityClass
When true
the rule will ignore JS classes that aren't class Components
Examples of correct code for this rule:
import { Bar } from "./Bar";
class Foo {
getBar() {
return <Bar />;
}
}
When false
(the default) the rule will flag any class with JSX
Examples of incorrect code for this rule:
import { Bar } from "./Bar";
class Foo {
getBar() {
return <Bar />;
}
}
PR's and issues welcomed! For more guidance check out CONTRIBUTING.md
See the project's MIT License.
FAQs
ESLint plugin that prevents the use of JSX class components
We found that eslint-plugin-react-prefer-function-component demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.