Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.0.13
->3.0.14
0.14.50
->0.14.51
Release Notes
evanw/esbuild
v0.14.51
Compare Source
Add support for React 17's
automatic
JSX transform (#334, #718, #1172, #2318, #2349)This adds support for the new "automatic" JSX runtime from React 17+ to esbuild for both the build and transform APIs.
New CLI flags and API options:
--jsx
,jsx
— Set this to"automatic"
to opt in to this new transform--jsx-dev
,jsxDev
— Toggles development mode for the automatic runtime--jsx-import-source
,jsxImportSource
— Overrides the root import for runtime functions (default"react"
)New JSX pragma comments:
@jsxRuntime
— Sets the runtime (automatic
orclassic
)@jsxImportSource
— Sets the import source (only valid with automatic runtime)The existing
@jsxFragment
and@jsxFactory
pragma comments are only valid with "classic" runtime.TSConfig resolving:
Along with accepting the new options directly via CLI or API, option inference from
tsconfig.json
compiler options was also implemented:"jsx": "preserve"
or"jsx": "react-native"
→ Same as--jsx=preserve
in esbuild"jsx": "react"
→ Same as--jsx=transform
in esbuild (which is the default behavior)"jsx": "react-jsx"
→ Same as--jsx=automatic
in esbuild"jsx": "react-jsxdev"
→ Same as--jsx=automatic --jsx-dev
in esbuildIt also reads the value of
"jsxImportSource"
fromtsconfig.json
if specified.For
react-jsx
it's important to note that it doesn't implicitly disable--jsx-dev
. This is to support the case where a user sets"react-jsx"
in theirtsconfig.json
but then toggles development mode directly in esbuild.esbuild vs Babel vs TS vs...
There are a few differences between the various technologies that implement automatic JSX runtimes. The JSX transform in esbuild follows a mix of Babel's and TypeScript's behavior:
When an element has
__source
or__self
props:Element has an "implicit true" key prop, e.g.
<a key />
:Element has spread children, e.g.
<a>{...children}</a>
Also note that TypeScript has some bugs regarding JSX development mode and the generation of
lineNumber
andcolumnNumber
values. Babel's values are accurate though, so esbuild's line and column numbers match Babel. Both numbers are 1-based and columns are counted in terms of UTF-16 code units.This feature was contributed by @jgoz.
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.