Fix parsing of <
after object literals with the jsx
plugin
#14557
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.
When parsing
({}<x)
with jsx plugin, Babel incorrectly marks<x
as a jsxTagStart token. In token definitions we have}
'sbeforeExpr
set totrue
, which then causesstate.canStartJSXElement
betrue
in theupdateContext
hook. In this PR we explicitly setstate.canStartJSXElement
to betrue
immediately before}
is consumed as the boundary between JS expression and jsx elements. Now in the({}<x)
, the<
token after}
can be correctly tokenized astt.lt
because it is parsed within normal JS routines.