---

This section details on the original issue you should resolve

<issue_title>JSX Fragments are in-properly typed with<></> syntax, when usingreact-jsx JSX option</issue_title>
<issue_description>### 🔎 Search Terms

JSX, Fragment, children type

🕗 Version & Regression Information

Bug exists since TypeScript introduces"jsx": "react-jsx" from version 4.1.2 untilnext version (6.0.0-dev.20250830).

⏯ Playground Link

https://stackblitz.com/edit/stackblitz-starters-sffhmvvz?file=index.tsx

💻 Code

import{Fragment}from"@/jsx-runtime";<Fragment>{"ok"}{({ foo})=>"also ok"}</Fragment>;<>{"ok"}{({ foo})=>"not ok"}{/* ^ Binding element 'foo' implicitly has an 'any' type. */}</>;

With following@/jsx-runtime definition:

exportconstjsx=(...args:unknown[])=>{};typeJsxElement=|JsxElementArray|undefined|string|((arg:{foo:"bar "})=>void);interfaceJsxElementArrayextendsArray<JsxElement>{}interfaceFragmentProps{children?:JsxElement;}exportconstFragment=(props:FragmentProps)=>{};

and tsconfig:

{"compilerOptions": {"strict":true,"jsx":"react-jsx","jsxImportSource":"@",// [...]  }}

🙁 Actual behavior

The first JSX expression using<Fragment> pass the type checking while the second JSX using<> syntax reports error due to it's children was typed toany:

index.tsx:10:7 - error TS7031: Binding element 'foo' implicitly has an 'any' type.10   {({ foo }) => "not ok"}         ~~~Found 1 error in index.tsx:10

🙂 Expected behavior

These two JSX expressions should both pass the type checking.

Additional information about the issue

This issue was first mentioned at#50429 and fixed in#59933, but the fix only take effects on"jsx": "react" not"jsx": "react-jsx", while the latter is a more encouraged approach in a modern project.</issue_description>

<agent_instructions>Read the crosslinked issues and PRs, construct a test case that shows the issue and commit it, then work to fix the bug.</agent_instructions>

Comments on the Issue (you are@copilot in this section)