![require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages](https://cdn.sanity.io/images/cgdhsj6q/production/be8ab80c8efa5907bc341c6fefe9aa20d239d890-1600x1097.png?w=400&fit=max&auto=format)
Security News
require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
@fossamagna/eslint-plugin-react-usememo
Advanced tools
This plugin enforces the wrapping of complex objects or functions (which might generate unnecessary renders or side-effects) in `useMemo` or `useCallback`. It also allows you to programmatically enforce the wrapping of functional components in `memo`, and
This plugin enforces the wrapping of complex objects or functions (which might generate unnecessary renders or side-effects) in useMemo
or useCallback
. It also allows you to programmatically enforce the wrapping of functional components in memo
, and that all props and dependencies are wrapped in useMemo
/useCallback
.
The objective is to ensure that your application's component tree and/or expensive lifecycles (such as React Native's FlatLists, useEffect, useMemo, etc.) only re-calculate or render again when absolutely necessary. By controlling expensive expressions, you can achieve optimal scalability and performance for your application.
Note: Use of memoization everywhere is not advised, as everything comes with a cost. Overusing memoization might slow down your application instead of speeding it up.
For more details, please refer to React's documentation on hooks, re-rendering and memoization.
Variables or expressions that return non-primitive objects or functions passed as props to other components.
Incorrect
function Component({incomingData}) {
const complexData = {
...incomingData,
checked: true
}; // generated each render, breaks hooks shallow comparison
return <SomeComponent data={complexData} />
}
Correct
function Component({incomingData}) {
const complexData = useMemo(() => ({
...incomingData,
checked: true
}), [incomingData]); // generated only when incomingData changes
return <SomeComponent data={complexData} />
}
Variables or expressions that return non-primitive objects returned from custom hooks.
Incorrect
function useMyData({incomingData}) {
const parsedData = parseData(incomingData); // generated each render
return parsedData; // Will result in loops passed as a dependency in other hooks(e.g. useMemo, useCallback, useEffect).
}
Correct
function useMyData({incomingData}) {
const parsedData = useMemo(() => parseData(incomingData), [incomingData]); // generated only when incomingData changes
return parsedData; // Won't generate loops if used as a dependency in hooks.
}
When the resulting value (expression or variable) is primitive (string, number, boolean).
Incorrect
function Component() {
const width = useMemo(() => someValue * 10, []); // results in integer, wouldn't break hooks' shallow comparison; Memoizing this would only reduce performance
return <SomeComponent width={width} />
}
Correct
function Component() {
const width = someValue * 10;
return <SomeComponent width={width} />
}
If you're passing props to a native component of the framework (e.g. Div, Touchable, etc), except in some instances in react-native (e.g. FlatList).
Incorrect
function Component() {
const onClick = useCallback(() => {}, []);
return <div onClick={onClick} />
}
Correct
function Component() {
const onClick = () => {};
return <div onClick={onClick} />
}
Values that can be a global/context outside the react Context. Incorrect
function Component() {
const breakpoints = [100];
return <Modal breakpoints={breakpoints}>
}
Correct
const breakpoints = [100];
function Component() {
return <Modal breakpoints={breakpoints}>
}
Install it with yarn:
yarn add @arthurgeron/eslint-plugin-react-usememo --dev
or npm:
npm install @arthurgeron/eslint-plugin-react-usememo --save-dev
Add the plugin to your eslintrc
file:
"plugins": ["@arthurgeron/react-usememo"],
Then enable any rules as you like:
"rules": {
"@arthurgeron/react-usememo/require-usememo": [2],
},
In this guide, we will cover three rules - require-usememo
, require-memo
, and require-usememo-children
.
require-usememo
(recommended)This rule requires complex values (objects, arrays, functions, and JSX) that get passed props or referenced as a hook dependency to be wrapped in useMemo() or useCallback().
One of the great features of this rule is its amazing autofix functionality. It intelligently wraps necessary components with useMemo() or useCallback(), making your code more efficient and saving you valuable time.
For detailed examples, options available for this rule, and information about the autofix functionality, please refer to our rules documentation.
require-memo
This rule requires all function components to be wrapped in React.memo()
.
For detailed examples and usage of this rule, please refer to our rules documentation
require-usememo-children
This rule requires complex values (objects, arrays, functions, and JSX) that get passed as children to be wrapped in useMemo()
or useCallback()
.
For detailed examples and options available for this rule, please refer to our rules documentation.
By efficiently using useMemo
, useCallback
, and React.memo()
, we can optimize our React and React Native applications. It allows us to control the re-calculation and re-rendering of components, offering better scalability and performance.
FAQs
This plugin enforces the wrapping of complex objects or functions (which might generate unnecessary renders or side-effects) in `useMemo` or `useCallback`. It also allows you to programmatically enforce the wrapping of functional components in `memo`, and
The npm package @fossamagna/eslint-plugin-react-usememo receives a total of 0 weekly downloads. As such, @fossamagna/eslint-plugin-react-usememo popularity was classified as not popular.
We found that @fossamagna/eslint-plugin-react-usememo demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
Security News
PyPI now supports iOS and Android wheels, making it easier for Python developers to distribute mobile packages.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.