chore(deps): update dependency eslint-plugin-react-refresh to v0.5.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-react-refresh	0.4.16 → 0.5.4

---

Release Notes

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

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

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,
];

v0.4.20

Compare Source

• Don't warn on nested HOC calls (fixes #​79)
• Fix false positive with as const (fixes #​80)

v0.4.19

Compare Source

Add name to configs for ESLint Config Inspector

v0.4.18

Compare Source

ESM/CJS interop is the worse that happened to this ecosystem, this is all I have to say.

v0.4.17

Compare Source

• Fix detection of local components to not generate warning on for variable inside JSX files that follow React component naming (fixes #​75)
• Update types to not require extra unnecessary .default property access under TS node16 module resolution (fixes #​70)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR is behind base branch, 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]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Progress: resolved 1, reused 0, downloaded 0, added 0
 WARN  deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
Progress: resolved 89, reused 0, downloaded 0, added 0
Progress: resolved 166, reused 0, downloaded 0, added 0
Progress: resolved 348, reused 0, downloaded 0, added 0
Progress: resolved 496, reused 0, downloaded 0, added 0
Progress: resolved 538, reused 0, downloaded 0, added 0
Progress: resolved 747, reused 0, downloaded 0, added 0
Progress: resolved 769, reused 0, downloaded 0, added 0
Progress: resolved 872, reused 0, downloaded 0, added 0
Progress: resolved 924, reused 0, downloaded 0, added 0
 WARN  9 deprecated subdependencies found: @humanwhocodes/config-array@0.13.0, @humanwhocodes/object-schema@2.0.3, @ungap/structured-clone@1.2.0, glob@10.3.10, glob@10.4.5, glob@7.2.3, inflight@1.0.6, rimraf@3.0.2, uuid@9.0.1
Progress: resolved 924, reused 0, downloaded 0, added 0, done

 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
└─┬ eslint-plugin-react-refresh 0.5.4
  └── ✕ unmet peer eslint@"^9 || ^10": found 8.57.1

hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.