chore(deps-dev): bump eslint-plugin-react-x from 2.3.11 to 5.10.3

[dependabot]

Bumps eslint-plugin-react-x from 2.3.11 to 5.10.3.

Release notes

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

v5.10.3 (2026-07-04)

What's Changed

🏗️ Internal

• Bumped typescript-eslint packages to ^8.62.1.
• Bumped @effect/language-service to ^0.86.3.
• Bumped undici and undici-types to ^8.6.0.
• Updated the @eslint-react/eslint-plugin package description.

Full Changelog: Rel1cx/eslint-react@v5.10.2...v5.10.3

Attestation

https://github.com/Rel1cx/eslint-react/attestations/33846197

v5.10.2 (2026-07-03)

What's Changed

🐞 Fixes

• Fixed an issue where several rules treated computed identifier keys in spread props (e.g. <div {...{ [key]: value }} />) as static prop names. The actual property name is the runtime value of the variable; computed string literal keys are still recognized. Affected rules:
  • react-x/no-missing-key
  • react-jsx/no-children-prop-with-children
  • react-jsx/no-children-prop
  • react-jsx/no-useless-fragment
  • react-dom/no-dangerously-set-innerhtml-with-children
  • react-dom/no-dangerously-set-innerhtml
  • react-dom/no-missing-button-type
  • react-dom/no-missing-iframe-sandbox
  • react-dom/no-string-style-prop
  • react-dom/no-unsafe-iframe-sandbox
  • react-dom/no-unsafe-target-blank
  • react-dom/no-void-elements-with-children
  • react-web-api/no-leaked-event-listener
  • react-web-api/no-leaked-fetch
• Fixed react-x/unsupported-syntax to no longer report IIFEs in JSX. This makes the rule consistent with the upstream react-hooks/unsupported-syntax and removes the iife message.

✨ New

• react-x/unsupported-syntax now detects eval calls via globalThis.eval, globalThis["eval"], and type assertions like (globalThis as any).eval.

🏗️ Internal

• Added an optional resolve parameter to Extract.getPropertyName so callers can control how identifier and private identifier property names are resolved.
• Added unit tests for Extract.getPropertyName.

... (truncated)

Changelog

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

v5.10.3 (2026-07-04)

🏗️ Internal

• Bumped typescript-eslint packages to ^8.62.1.
• Bumped @effect/language-service to ^0.86.3.
• Bumped undici and undici-types to ^8.6.0.
• Updated the @eslint-react/eslint-plugin package description.

Full Changelog: Rel1cx/eslint-react@v5.10.2...v5.10.3

v5.10.2 (2026-07-03)

🐞 Fixes

• Fixed an issue where several rules treated computed identifier keys in spread props (e.g. <div {...{ [key]: value }} />) as static prop names. The actual property name is the runtime value of the variable; computed string literal keys are still recognized. Affected rules:
  • react-x/no-missing-key
  • react-jsx/no-children-prop-with-children
  • react-jsx/no-children-prop
  • react-jsx/no-useless-fragment
  • react-dom/no-dangerously-set-innerhtml-with-children
  • react-dom/no-dangerously-set-innerhtml
  • react-dom/no-missing-button-type
  • react-dom/no-missing-iframe-sandbox
  • react-dom/no-string-style-prop
  • react-dom/no-unsafe-iframe-sandbox
  • react-dom/no-unsafe-target-blank
  • react-dom/no-void-elements-with-children
  • react-web-api/no-leaked-event-listener
  • react-web-api/no-leaked-fetch
• Fixed react-x/unsupported-syntax to no longer report IIFEs in JSX. This makes the rule consistent with the upstream react-hooks/unsupported-syntax and removes the iife message.

✨ New

• react-x/unsupported-syntax now detects eval calls via globalThis.eval, globalThis["eval"], and type assertions like (globalThis as any).eval.

🏗️ Internal

• Added an optional resolve parameter to Extract.getPropertyName so callers can control how identifier and private identifier property names are resolved.
• Added unit tests for Extract.getPropertyName.

Full Changelog: Rel1cx/eslint-react@v5.10.1...v5.10.2

v5.10.1 (2026-07-03)

🐞 Fixes

• Added the missing static-components rule to disable-conflict-eslint-plugin-react-hooks, closes #1884.

📝 Documentation

... (truncated)

Commits

• a4130ee release: 5.10.3
• 3d6f501 release: 5.10.2
• ecb5626 release: 5.10.1
• 9973045 fix: static-components rule is missing from `disable-conflict-eslint-plugin...
• 0f237a6 chore(deps): bump typescript-eslint, @​types/node, vite and tailwindcss
• 3a5e3af release: 5.10.0
• 3973a19 refactor(var): move isInitializedFromReact helpers from core to var (#1883)
• 062e93a refactor(website): tidy component prop types
• 857fe27 chore(deps): bump tsl-dx from 0.13.1 to 0.13.2
• a40f3bf docs: fix 5.7.2 changelog entry for no-unused-state
• Additional commits viewable 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)

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
latterfix-frontend	Error		Jul 11, 2026 8:04am