chore(deps-dev): bump eslint-plugin-react-refresh from 0.4.20 to 0.5.2#918
Conversation
Bumps [eslint-plugin-react-refresh](https://github.com/ArnaudBarre/eslint-plugin-react-refresh) from 0.4.20 to 0.5.2. - [Release notes](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/releases) - [Changelog](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/main/CHANGELOG.md) - [Commits](ArnaudBarre/eslint-plugin-react-refresh@v0.4.20...v0.5.2) --- updated-dependencies: - dependency-name: eslint-plugin-react-refresh dependency-version: 0.5.2 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
| "eslint-plugin-jsx-a11y": "^6.10.2", | ||
| "eslint-plugin-react-hooks": "^5.2.0", | ||
| "eslint-plugin-react-refresh": "^0.4.14", | ||
| "eslint-plugin-react-refresh": "^0.5.2", |
There was a problem hiding this comment.
ESLint 8 incompatible with react-refresh 0.5.x peer requirement
High Severity
eslint-plugin-react-refresh v0.5.2 requires eslint: ^9 || ^10 as a peer dependency, but every package and example in this repo still depends on eslint: "^8.56.0" (resolving to 8.57.1). This is a breaking major version bump — the plugin now ships as ESM-only, requires flat config, and drops ESLint 8 support. All four packages and the guide-example will have unmet peer dependencies, and ESLint may fail to load the plugin at runtime.
Additional Locations (2)
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| "eslint": "^8.56.0", | ||
| "eslint-plugin-react-hooks": "^5.2.0", | ||
| "eslint-plugin-react-refresh": "^0.4.14", | ||
| "eslint-plugin-react-refresh": "^0.5.2", |
There was a problem hiding this comment.
Default import removed in v0.5 breaks ESLint config
High Severity
The bump to eslint-plugin-react-refresh@^0.5.2 removes the default export from the package. The existing examples/guide-example/eslint.config.js uses import reactRefresh from 'eslint-plugin-react-refresh' (a default import) and passes it directly as a plugin via 'react-refresh': reactRefresh. In v0.5.x, this default import returns undefined, causing an "Expected an object" error at lint time. The import needs to change to the named export (import { reactRefresh }) and the plugin reference needs to use reactRefresh.plugin.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #918 +/- ##
=======================================
Coverage 65.15% 65.15%
=======================================
Files 207 207
Lines 9593 9593
Branches 1250 1250
=======================================
Hits 6250 6250
Misses 3318 3318
Partials 25 25 |


Bumps eslint-plugin-react-refresh from 0.4.20 to 0.5.2.
Release notes
Sourced from eslint-plugin-react-refresh's releases.
... (truncated)
Changelog
Sourced from eslint-plugin-react-refresh's changelog.
... (truncated)
Commits
c0317bfFix support for nested function calls for extraHOCs [publish]42a1805Explicit v10 support (fixes #106) [publish]199793eSupport nested function calls for extraHOCs (fixes #104)26b3c15Support false positives with TypeScript function overloading (fixes #105)daa2efbRevamp logic to catch more cases [publish] (#97)95c02baRevert "Catch non React exports defined as call expressions"(fixes #95) [publ...8ea312dUpdate the name of next config (vite->next) (#96)4fc6d3dCatch non React exports defined as call expressions [publish]0397bdeAllow non-leading underscores (#94)6368815Add generate{ImageMetadata,Sitemaps,StaticParams} to Next config [publish] (#92)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for eslint-plugin-react-refresh since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)