npm / eslint-plugin-react-refresh
eslint-plugin-react-refresh
What changed in eslint-plugin-react-refresh 0.4 to 0.5, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-18.
4 breaking6 new APIs and options3 behavior and defaults1 tooling7 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli initeslint-plugin-react-refresh 0.515 changes
Breaking changes 4
The package now requires ESLint 9.
Replaces
customHOCs; use it to specify additional HOCs for validation.HOC call validation is stricter, distinguishing actual React HOC calls from random call expressions; add HOCs such as
connectorstyledtoextraHOCswhen needed.The package now requires Node 20.
New APIs and options 3
Adds an option that suppresses warnings when components are exported together in an object; every member must be a component, and anonymous functions need a component name as key. Defaults to false, or true in vite config.
Add instant to allowExportNames in Next config.
A named export provides the plugin object and configuration presets; its preset functions accept custom options, merge them with defaults, and return a config object.
Behavior and default changes 3
Re-exporting namespace components is now supported.
The Next config allowExportNames list now includes contentType and size.
Supports nested function calls for extraHOCs.
Tooling 1
ESLint v10 is now supported.
Fixes and other changes 4
SCREAMING_SNAKE_CASE constants exported via this syntax are no longer incorrectly treated as React components.
Fixes detection of non-component classes exported via export { }.
False positives with TypeScript function overloading are supported.
The rule now handles ternaries and chained HOC patterns such as
customHOC(props)(Component), allowing it to correctly support those files.
eslint-plugin-react-refresh 0.46 changes
New APIs and options 3
Adds generateImageMetadata to allowExportNames in Next config.
Adds generateSitemaps to allowExportNames in Next config.
Adds generateStaticParams to allowExportNames in Next config.
Fixes and other changes 3
Reverts changes intended to fix issue #93, addressing issue #95.
Component names may now contain underscores.
The rule now reports cases such as exporting Object.keys(TABLE) as EnumType[].