Skip to content
This repository was archived by the owner on Jun 23, 2025. It is now read-only.

Update dependency eslint-plugin-react-refresh to v0.4.20#293

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

Update dependency eslint-plugin-react-refresh to v0.4.20#293
renovate[bot] wants to merge 1 commit intomainfrom
renovate/eslint-plugin-react-refresh-0.x-lockfile

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Jun 15, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-react-refresh 0.4.4 -> 0.4.20 age adoption passing confidence

Release Notes

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

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)

v0.4.16

Compare Source

Fix CJS/ESM interop issue. Sorry everyone for the trouble.

v0.4.15

Compare Source

Add support for custom HOCs (#​60)

By default, the rule only knows that memo & forwardRef function calls with return a React component. With this option, you can also allow extra function names like Mobx observer to make this code valid:

const Foo = () => <></>;
export default observer(Foo);
{
  "react-refresh/only-export-components": [
    "error",
    { "customHOCs": ["observer"] }
  ]
}

Thanks @​HorusGoul!

Add recommended config and simple types (#​67)

You can now add the recommended config to your ESLint config like this:

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

export default [
  /* Main config */
  reactRefresh.configs.recommended, // Or reactRefresh.configs.vite for Vite users
];

To follow ESLint recommandations, the rule is added with the error severity.

Some simple types ensure that people typecheking their config won't need @ts-expect-error anymore.

Bump ESLint peer dependency to 8.40

This was actually done by mistake in the previous release when moving from a deprecated API to a new one.

Given that ESLint 8 is officialy end-of-life and the only report (#​56) didn't get likes, I'm going forward and documenting the expected minimum version from ESLin in the package JSON so that people can get warning from their package manager.

v0.4.14

Compare Source

v0.4.13

Compare Source

v0.4.12

Compare Source

  • Support type assertion on default export (fixes #​48)
  • Add default export to fix usage with jiti (fixes #​50)

v0.4.11

Compare Source

  • Ignore type exports (ex. export type foo = string;) (fixes #​47)

v0.4.10

Compare Source

  • Support function Foo() {}; export default React.memo(Foo) (#​46) (thanks @​SukkaW!)

v0.4.9

Compare Source

  • Support function Foo() {}; export default memo(Foo) (fixes #​44) (thanks @​SukkaW!)

v0.4.8

Compare Source

  • Support export const foo = -1 with allowConstantExport (fixes #​43)

v0.4.7

Compare Source

  • Support export { Component as default } (fixes #​41)

v0.4.6

Compare Source

  • Ignore cypress test files (#​39)

v0.4.5

Compare Source

  • Allow TaggedTemplateExpression for styled components (fixes #​32)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Jun 15, 2025

Deploying plarail2023 with  Cloudflare Pages  Cloudflare Pages

Latest commit: 9e43d99
Status: ✅  Deploy successful!
Preview URL: https://dbc6aa32.plarail2023.pages.dev
Branch Preview URL: https://renovate-eslint-plugin-react.plarail2023.pages.dev

View logs

@renovate renovate bot added the renovate By renovate bot label Jun 15, 2025
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Jun 15, 2025

⚠️ 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: frontend/dashboard/yarn.lock
error This project's package.json defines "packageManager": "yarn@pnpm@10.12.1". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.

@renovate renovate bot force-pushed the renovate/eslint-plugin-react-refresh-0.x-lockfile branch 15 times, most recently from e499edc to 503d943 Compare June 21, 2025 03:15
@renovate renovate bot force-pushed the renovate/eslint-plugin-react-refresh-0.x-lockfile branch from 503d943 to 9e43d99 Compare June 21, 2025 03:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

renovate By renovate bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants