fix(react-utilities): replace deprecated TypeScript assertion syntax#36185
Merged
Hotell merged 2 commits intoMay 11, 2026
Merged
Conversation
…es issues to babel tsx
|
Pull request demo site: URL |
📊 Bundle size report✅ No changes found |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
layershifter
approved these changes
May 11, 2026
mainframev
pushed a commit
to mainframev/fluentui
that referenced
this pull request
May 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Replaces the legacy TypeScript angle-bracket type assertion syntax (
<Type>expr) with theassyntax (expr as Type) inisVirtualElement.ts.The angle-bracket assertion syntax (
<VirtualElement>element) is invalid when processed by Babel's TSX parser — Babel interprets it as a JSX element rather than a type assertion. While TypeScript's own compiler handles it correctly in.tsfiles, this causes issues when the code is run through Babel (e.g., when testing out React Compiler integration).Change
Both forms are semantically identical in TypeScript, but only the
assyntax is compatible with Babel's TypeScript transform.