Preserve inline TypeScript enums as opaque pass-through HIR nodes, matching upstream React Compiler behavior. Apply Oxc-specific raw AST reference renaming, and skip compilation when passthrough would hide nested captures or flatten block-local bindings.
AI-assisted: Codex was used to implement and validate this change.
Follow-up to #24393, removing preserved-AST baggage from the HIR:
## Remove `UnsupportedNode`
Its only producer was the inline TS `enum` statement — upstream's single *silent* `UnsupportedNode` case (every other upstream site records an error first, so the function fails compilation anyway; this port already expresses those without the wrapper). Instead of carrying an AST statement through the whole pipeline just to re-emit it at codegen, inline enums now take the same path as `using` declarations: lowering sets `skip_compilation`, the function is left uncompiled — silently, no diagnostic — and the rest of the file compiles as usual.
One intended snapshot change: `ts-enum-inline.tsx` is no longer memoized and round-trips unchanged. (Top-level enums are unaffected — only compiled function bodies are rebuilt.)
## Align `TypeCastExpression` with the oxc AST
The stringly `(type_annotation_kind: Option<&'static str>, type_annotation: Option<&TSType>)` pair becomes a `TypeCast<'a>` enum mirroring the oxc wrapper nodes it lowers from — `TSAsExpression`/`TSTypeAssertion` → `TypeCast::As`, `TSSatisfiesExpression` → `TypeCast::Satisfies` — removing the invalid `None`/`Some` combinations and codegen's dead fallback arm. This leaves the cast annotation as the only borrowed AST kept in the HIR (an arena clone made at lowering).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
## Summary
`oxc_react_compiler` had no committed test over the upstream React
Compiler fixture corpus — the fixtures lived only in the
`oxc-project/forked-react-compiler` checkout, exercised out-of-tree.
That gap let real regressions slip past the 15 in-crate integration
tests. This PR closes it.
- **`crates/oxc_react_compiler/fixtures/`** — 1734 fixture *input* files
(`.js`/`.ts`/`.tsx`/`.jsx`/`.mjs`), copied from the fork's
`babel-plugin-react-compiler/src/__tests__/fixtures/compiler` tree with
subdirectories preserved. Flow fixtures (the `@flow`-pragma ones) are
excluded — oxc has no Flow parser. The upstream `.expect.md` goldens are
also not copied; insta is the golden here.
- **`crates/oxc_react_compiler/tests/snapshot.rs`** — an `insta::glob!`
test that, per fixture, derives `PluginOptions`/`EnvironmentConfig` from
the first-line `// @directive` pragmas (base `compilationMode=all` /
`panicThreshold=all_errors`, matching the upstream `snap` runner),
parses → builds semantic → runs `transform`, and snapshots the compiled
output plus diagnostics. Unrecognised directives are ignored, as
upstream does; camelCase flag directives map to `EnvironmentConfig`
fields via `convert_case`.
- **`crates/oxc_react_compiler/tests/snapshots/`** — 1734 committed
`.snap` goldens (oxc's own output).
- **`.typos.toml`** — excludes the fixtures dir (the upstream fixtures
contain intentional typos; `**/*.snap` was already excluded).
These snapshots are oxc's own golden output, so `cargo test` (and CI)
now catches any change in compiler behaviour across the corpus.
Regenerate after an intended change with `cargo insta accept`.
## Verification
- `cargo test -p oxc_react_compiler` passes — the 1734-fixture snapshot
test plus the existing 15 integration tests; also green under
`--all-features` (matches the cross-target CI job).
- clippy `-D warnings`, `cargo fmt`, and `typos` clean.
- No fixture panics; 1336 compiled / 398 unchanged / 335 with
diagnostics.
- The `error.*` fixtures capture the exact diagnostics — including the
"Cannot reassign variable after render" error that a recent scoping
change had silently suppressed, confirming the suite catches real
regressions.
---
AI usage disclosure: authored with Claude Code and reviewed before
submission.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Boshen