florian/scum-quest-web

Fork 0

Update dependency eslint-plugin-react-refresh to ^0.5.0 #5

Open

renovate wants to merge 1 commit from renovate/eslint-plugin-react-refresh-0.x into main

renovate commented

2026-06-14 03:54:33 +02:00

Collaborator

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-react-refresh	`^0.4.19` → `^0.5.0`

Release Notes

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

`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"] }]
}

`v0.4.26`

Compare Source

Revert changes to fix #93 (fixes #95)

`v0.4.25`

Compare Source

Report cases like export const ENUM = Object.keys(TABLE) as EnumType[]; (fixes #93) (reverted in 0.4.26)
Allow _ in component names (#94)

`v0.4.24`

Compare Source

Add "generateImageMetadata", "generateSitemaps" & "generateStaticParams" to allowExportNames in Next config

`v0.4.23`

Compare Source

Add "metadata", "generateMetadata" & "generateViewport" to allowExportNames in Next config

`v0.4.22`

Compare Source

Add "viewport" to allowExportNames in Next config (#89)

`v0.4.21`

Compare Source

Add Next config (fixes #85)

This allows exports like fetchCache and revalidate which are used in Page or Layout components and don't trigger a full page reload.

import reactRefresh from "eslint-plugin-react-refresh";

export default [
  /* Main config */
  reactRefresh.configs.next,
];

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
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 has been generated by Mend Renovate.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [eslint-plugin-react-refresh](https://github.com/ArnaudBarre/eslint-plugin-react-refresh) | [`^0.4.19` → `^0.5.0`](https://renovatebot.com/diffs/npm/eslint-plugin-react-refresh/0.4.20/0.5.2) | ![age](https://developer.mend.io/api/mc/badges/age/npm/eslint-plugin-react-refresh/0.5.2?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/eslint-plugin-react-refresh/0.4.20/0.5.2?slim=true) | --- ### Release Notes <details> <summary>ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)</summary> ### [`v0.5.2`](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#052) [Compare Source](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.5.1...v0.5.2) - Support nested function calls for extraHOCs (actually fixes [#104](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/issues/104)) ### [`v0.5.1`](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#051) [Compare Source](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.5.0...v0.5.1) - Mark ESLint v10 as supported - Support false positives with TypeScript function overloading (fixes [#105](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/issues/105)) - Support nested function calls for extraHOCs (fixes [#104](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/issues/104)) ### [`v0.5.0`](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#050) [Compare Source](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.4.26...v0.5.0) ##### 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](https://eslint.org/docs/latest/use/configure/migration-guide) - 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: ```js 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: ```js 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](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/issues/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](https://github.com/eclipse-apoapsis/ort-server/blob/ddfc624ce71b9f2ca6bad9b8c82d4c3249dd9c8b/ui/src/routes/__root.tsx) given this config: ```json { "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](https://github.com/TanStack/router/blob/8628d0189412ccb8d3a01840aa18bac8295e18c8/packages/react-router/src/route.tsx#L263) 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](https://bsky.app/profile/arnaud-barre.bsky.social/post/3ma5h5tf2sk2e). 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: ```json { "react-refresh/only-export-components": ["warn", { "extraHOCs": ["connect"] }] } ``` ### [`v0.4.26`](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#0426) [Compare Source](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.4.25...v0.4.26) - Revert changes to fix [#93](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/issues/93) (fixes [#95](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/issues/95)) ### [`v0.4.25`](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#0425) [Compare Source](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.4.24...v0.4.25) - Report cases like `export const ENUM = Object.keys(TABLE) as EnumType[];` (fixes [#93](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/issues/93)) (reverted in 0.4.26) - Allow `_` in component names ([#94](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/pull/94)) ### [`v0.4.24`](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#0424) [Compare Source](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.4.23...v0.4.24) - Add `"generateImageMetadata"`, `"generateSitemaps"` & `"generateStaticParams"` to `allowExportNames` in Next config ### [`v0.4.23`](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#0423) [Compare Source](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.4.22...v0.4.23) - Add `"metadata"`, `"generateMetadata"` & `"generateViewport"` to `allowExportNames` in Next config ### [`v0.4.22`](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#0422) [Compare Source](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.4.21...v0.4.22) - Add `"viewport"` to `allowExportNames` in Next config ([#89](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/pull/89)) ### [`v0.4.21`](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#0421) [Compare Source](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.4.20...v0.4.21) - Add Next config (fixes [#85](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/issues/85)) This allows exports like `fetchCache` and `revalidate` which are used in Page or Layout components and don't trigger a full page reload. ```js import reactRefresh from "eslint-plugin-react-refresh"; export default [ /* Main config */ reactRefresh.configs.next, ]; ``` </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - 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 has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).

renovate added 1 commit

2026-06-14 03:54:33 +02:00

Update dependency eslint-plugin-react-refresh to ^0.5.0 ac479ad5c1

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/eslint-plugin-react-refresh-0.x:renovate/eslint-plugin-react-refresh-0.x

git switch renovate/eslint-plugin-react-refresh-0.x

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff renovate/eslint-plugin-react-refresh-0.x

git switch renovate/eslint-plugin-react-refresh-0.x

git rebase main

git switch main

git merge --ff-only renovate/eslint-plugin-react-refresh-0.x

git switch renovate/eslint-plugin-react-refresh-0.x

git rebase main

git switch main

git merge --no-ff renovate/eslint-plugin-react-refresh-0.x

git switch main

git merge --squash renovate/eslint-plugin-react-refresh-0.x