Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat(linter/react): Update lint rules to accomodate changes in React 19.3 - #26571

Open
connorshea wants to merge 3 commits into
mainfrom
feat/react-19-3
Open

feat(linter/react): Update lint rules to accomodate changes in React 19.3#26571
connorshea wants to merge 3 commits into
mainfrom
feat/react-19-3

Conversation

@connorshea

@connorshea connorshea commented Sep 11, 2026

Copy link
Copy Markdown
Member

Fix #26570. See the React 19.3 blog post for more details: https://react.dev/blog/2026/09/09/react-19-3

Generated with help from Claude Code.

react/jsx-no-useless-fragment is updated so that the new ref prop is handled and exempted in the same way as key already was.

// This is no longer useless.
return <Fragment ref={fragRef}>Foobarbaz</Fragment>;

And react/no-unknown-property is updated to support various new DOM properties added in 19.3:

  • onFullscreenChange
  • onFullscreenError
  • onFullscreenChangeCapture
  • onFullscreenErrorCapture
  • credentialless on <iframe>s (but NOT credentialLess, only the lowercase version should work)
  • maskType on <mask>s

This is a special prop similar to `key` as of React 19.3, so it means the fragment is not useless and thus should not be considered a violation.

See https://react.dev/blog/2026/09/09/react-19-3#fragment-refs
…erties added in React 19.3.

A variety of properties added in React 19.3 are now valid for usage, so we should add them to the allowed map.

See https://react.dev/blog/2026/09/09/react-19-3
@connorshea
connorshea requested a review from camc314 as a code owner September 11, 2026 22:31
@github-actions github-actions Bot added the A-linter Area - Linter label Sep 11, 2026
@codspeed-hq

codspeed-hq Bot commented Sep 11, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 5 untouched benchmarks
⏩ 76 skipped benchmarks1


Comparing feat/react-19-3 (eb17a14) with main (071ac78)

Open in CodSpeed

Footnotes

  1. 76 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@connorshea
connorshea added this pull request to stack #26573 September 11, 2026 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-linter Area - Linter

Projects

None yet

Development

Successfully merging this pull request may close these issues.

linter(react): Update rules to accomodate React 19.3 changes

1 participant