Skip to content

chore(deps): update dependency eslint-plugin-react-refresh to ^0.5.0 - #166

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/eslint-plugin-react-refresh-0.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/eslint-plugin-react-refresh-0.x

Conversation

@renovate

@renovate renovate Bot commented Feb 3, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
eslint-plugin-react-refresh ^0.4.5 → ^0.5.0 age confidence

Release Notes

ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)

v0.5.8

Compare Source

  • Handle more cases in export default declaration (fixes #​119)

v0.5.7

Compare Source

Add allowCompoundComponents option (#​117)

Default: false (true in vite config)

Don't warn when components are exported as an object gathering them. Every member of the object must be a component, and a member holding an anonymous function requires a component name as key.

This should be enabled if the fast refresh implementation correctly handles this case. Vite supports it since @vitejs/plugin-react 4.7.0, @vitejs/plugin-react-swc 3.11.0.

{
  "react-refresh/only-export-components": [
    "error",
    { "allowCompoundComponents": true }
  ]
}

Enabling this option allows code such as the following:

const Root = () => <></>;
const Label = () => <></>;
export const Tag = { Root, Label };

v0.5.6

Compare Source

  • Support re-exporting namespace components (fixes #​116)

v0.5.5

Compare Source

  • Fix SCREAMING_SNAKE_CASE constant exported via export { Name } incorrectly treated as React component #​114 (fixes #​113)
  • Add contentType and size to allowExportNames in Next config #​115

v0.5.4

Compare Source

  • Add instant to allowExportNames in Next config #​112

v0.5.3

Compare Source

  • Fix check for non component class exported via export { } #​110 (fixes #​109)

v0.5.2

Compare Source

  • Support nested function calls for extraHOCs (actually fixes #​104)

v0.5.1

Compare Source

  • Mark ESLint v10 as supported
  • Support false positives with TypeScript function overloading (fixes #​105)
  • Support nested function calls for extraHOCs (fixes #​104)

v0.5.0

Compare Source

Breaking changes
  • The package now ships as ESM and requires ESLint 9 + node 20. Because legacy config doesn't support ESM, this requires to use flat config
  • A new reactRefresh export is available and prefered over the default export. It's an object with two properties:
    • plugin: The plugin object with the rules
    • configs: An object containing configuration presets, each exposed as a function. These functions accept your custom options, merge them with sensible defaults for that config, and return the final config object.
  • customHOCs option was renamed to extraHOCs
  • Validation of HOCs calls is now more strict, you may need to add some HOCs to the extraHOCs option

Config example:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";

export default defineConfig(
  /* Main config */
  reactRefresh.configs.vite({ extraHOCs: ["someLibHOC"] }),
);

Config example without config:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";

export default defineConfig({
  files: ["**/*.ts", "**/*.tsx"],
  plugins: {
    // other plugins
    "react-refresh": reactRefresh.plugin,
  },
  rules: {
    // other rules
    "react-refresh/only-export-components": [
      "warn",
      { extraHOCs: ["someLibHOC"] },
    ],
  },
});
Why

This version follows a revamp of the internal logic to better make the difference between random call expressions like export const Enum = Object.keys(Record) and actual React HOC calls like export const MemoComponent = memo(Component). (fixes #​93)

The rule now handles ternaries and patterns like export default customHOC(props)(Component) which makes it able to correctly support files like this one given this config:

{
  "react-refresh/only-export-components": [
    "warn",
    { "extraHOCs": ["createRootRouteWithContext"] }
  ]
}

[!NOTE]
Actually createRoute functions from TanStack Router are not React HOCs, they return route objects that fake to be a memoized component but are not. When only doing createRootRoute({ component: Foo }), HMR will work fine, but as soon as you add a prop to the options that is not a React component, HMR will not work. I would recommend to avoid adding any TanStack function to extraHOCs it you want to preserve good HMR in the long term. Bluesky thread.

Because I'm not 100% sure this new logic doesn't introduce any false positive, this is done in a major-like version. This also give me the occasion to remove the hardcoded connect from the rule. If you are using connect from react-redux, you should now add it to extraHOCs like this:

{
  "react-refresh/only-export-components": ["warn", { "extraHOCs": ["connect"] }]
}

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
    • Only on Sunday and Saturday (* * * * 0,6)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch from 2a50b4c to 43c5fc2 Compare February 12, 2026 11:41
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch 2 times, most recently from 299f79f to 3ef7ecc Compare February 23, 2026 23:04
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch 3 times, most recently from 023bef1 to 8fe8927 Compare March 17, 2026 12:18
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch from 8fe8927 to 57910e6 Compare April 29, 2026 11:59
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch from 57910e6 to 0f91244 Compare June 14, 2026 13:43
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch from 0f91244 to bbb5ba2 Compare July 24, 2026 21:50
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch 2 times, most recently from ec45f33 to 347c440 Compare August 10, 2026 13:59
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch 2 times, most recently from 8a0994e to 9169b5a Compare September 2, 2026 11:11
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch from 9169b5a to ce9d72c Compare September 14, 2026 19:44
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch from ce9d72c to ddee265 Compare September 25, 2026 04:42
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch from ddee265 to e8cec1d Compare November 5, 2026 23:34
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-react-refresh-0.x branch from e8cec1d to 6912868 Compare November 15, 2026 10:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants