fix(deps-dev): bump eslint-plugin-react-refresh from 0.5.3 to 0.5.7

[dependabot]

Bumps eslint-plugin-react-refresh from 0.5.3 to 0.5.7.

Release notes

Sourced from eslint-plugin-react-refresh's releases.

v0.5.7

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

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

v0.5.5

• 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

• Add instant to allowExportNames in Next config #112

Changelog

Sourced from eslint-plugin-react-refresh's changelog.

0.5.7

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 };

0.5.6

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

0.5.5

• 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

0.5.4

• Add instant to allowExportNames in Next config #112

Commits

• fd40d83 Add allowCompoundComponents option [publish] (#117)
• 620568a Support re-exporting namespace components (fixes #116) [publish]
• 65c3172 [publish] v0.5.5
• 8411020 Bump deps
• c28fa15 Fix SCREAMING_SNAKE_CASE constant exported via export { Name } incorrectly ...
• 554c764 [publish] add contentType and size to allowExportNames in Next config (#115)
• e316617 [publish] Add instant to allowExportNames in Next config (#112)
• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

📝 Summary by GitNexus

Summary

A narrowly scoped development dependency update with no traced downstream reach. Review attention is centered on dependency metadata and the lockfile.

🟡 MEDIUM blast radius. This updates the development dependency eslint-plugin-react-refresh in package.json and pnpm-lock.yaml, with no graph dependents.

Review package.json alongside pnpm-lock.yaml to check that the dependency version is represented consistently. No affected execution flows or cross-repo consumers were found.

Added by GitNexus for PR #918. Edit freely — this block is replaced on the next review, everything above it is left untouched.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
do-knowledge-studio	Ready	Preview, v0	Oct 6, 2026 6:05am UTC

[github-actions]

Blocked merge diagnosis — blocked
⏳ Check run(s) still in progress: ["Codacy Static Code Analysis","labeler","commitlint","GitHub Actions Workflow Validation","Diagnose Blocked Merge State","Detect Changes","YAML Syntax Validation","Trivy Filesystem Security Scan","Dependency Advisory Audit","Infrastructure as Code Security","Secret Detection","Shell Script Security Analysis","Analyze (javascript-typescript)","Analyze (actions)","GitNexus"]

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[nexus-check]

GitNexus Review · PR #918

No issues found in 2 changed files. (target branch indexed; the incoming branch is not, so cross-branch structure came from the diff alone)

Summary

A narrowly scoped development dependency update with no traced downstream reach. Review attention is centered on dependency metadata and the lockfile.

🟡 MEDIUM blast radius. This updates the development dependency eslint-plugin-react-refresh in package.json and pnpm-lock.yaml, with no graph dependents.

Review package.json alongside pnpm-lock.yaml to check that the dependency version is represented consistently. No affected execution flows or cross-repo consumers were found.

Full detail lives in the GitNexus check run for this commit.

[nexus-check]

🤖 Agent context for GitNexus Review · PR #918

This comment carries deterministic graph detail for coding agents and reviewers who want the receipts — the main review comment carries the human summary.

🟡 MEDIUM blast radius — no downstream dependents were found in the code graph; a spot-check of the dependents should cover it. (likely driven by file-risk heuristics — no direct dependents or affected modules were found)

Blast Level	Dependents	Modules	Files
🟡 MEDIUM	0	0	2

What changed

Changed Files (2)

File	Status
package.json	🟡 modified
pnpm-lock.yaml	🟡 modified

What to check

File Risk (2)

File	Risk	Category
package.json	🟡 MEDIUM	Dependencies
pnpm-lock.yaml	🟢 LOW	Lock File