Support the Oxc React Compiler in @astrojs/react

[hanford]

What problem does this solve?

I'd like to enable the Oxc React Compiler directly through @astrojs/react, without writing a separate Vite transform or changing existing Babel configuration.

Proposed API

import react from '@astrojs/react';
import { defineConfig } from 'astro/config';

export default defineConfig({
  integrations: [react({ compiler: true })],
});

Users would install oxc-transform-react, plus react-compiler-runtime for React 17/18. An options object should also be accepted for compiler configuration.

Compatibility

This should be an opt-in, non-breaking addition. Existing projects should keep working without configuration changes, including projects using custom Babel plugins or Babel configuration callbacks.

Vite's React plugin supports the Oxc compiler in v6, but that version removes the babel option. Keeping Astro's current React plugin and adding an Oxc transform ahead of it would let us expose the compiler without requiring that migration.

Compilation should apply to client components, respect the integration's file filters, and preserve hydration and Fast Refresh. The scope is @astrojs/react.

Related work

Implementation: #17951. It preserves Babel support and includes a minor changeset.

Related: #14955 proposes an option for the Babel-based React Compiler.

[astro-factory]

Triage complete

• Prepare the workspace: ready
• Install dependencies: complete
• Build the project: complete
• Reproduce the issue: skipped (not actionable)
• Diagnose the cause: not needed (reproduction was skipped)
• Verify the diagnosis: not needed (reproduction was skipped)
• Attempt a fix: not needed (reproduction was skipped)
• Publish the result: set triage: not actionable

---

• Reproduced: Skipped — this is a feature request, not a bug report
• Exploration: No — not applicable for feature requests
• Unit Test: No — not applicable for feature requests
• Priority: P2: nice to have. This is a feature request to upgrade @astrojs/react to @vitejs/plugin-react v6 and expose the Oxc-based React Compiler option. It doesn't represent broken functionality.

This issue is a feature request, not a bug report. It proposes upgrading @astrojs/react to use @vitejs/plugin-react v6 (which switches to an Oxc pipeline for JSX/Fast Refresh) and exposing the native React Compiler as an opt-in compiler option. The author notes this would be a major release since v6 removes the babel option. An implementation PR (#17951) has already been submitted.

I was unable to determine the cause of this issue. Automated triage is designed for bug reports and cannot meaningfully process feature requests. The linked PR #17951 appears to contain the proposed implementation.

Full Triage Report

Issue Title

Support the Oxc React Compiler in @astrojs/react

Issue Author

@hanford

Issue Description

This is a feature request (not a bug report) asking to:

1. Upgrade @astrojs/react to @vitejs/plugin-react v6 so JSX and Fast Refresh use its Oxc pipeline.
2. Expose the native Oxc-based React Compiler as an opt-in option in the Astro config:

import react from '@astrojs/react';
import { defineConfig } from 'astro/config';

export default defineConfig({
  integrations: [react({ compiler: true })],
});

The author notes this would be a major release because v6 of @vitejs/plugin-react removes the babel option. Users with custom Babel transforms would need migration guidance.

Related work

• Implementation PR: feat(react): add opt-in OXC React Compiler support #17951
• Related issue: feat(config): Add React compiler as an Astro config option #14955 (proposes an option for the Babel-based React Compiler; this proposal uses the native Oxc implementation)

Reproduction Status: SKIPPED

Reason: not-actionable

This issue is a feature request, not a bug report. The issue template sections used are "What problem does this solve?" and "Proposed change" — the standard feature request template. There is no bug described, no expected vs actual behavior, no error messages, and no reproduction steps. The triage workflow can only process bug reports.

Environment

N/A — no environment details provided (not applicable for a feature request).

Steps Attempted

None — early exit due to not-actionable (feature request).

Expected vs Actual Result

N/A — this is a feature request, not a bug report.

Error Messages

None.

This report was made by an LLM. The analysis may be wrong, and the potential fix might not work, but is intended as a starting point for exploring the issue.

[matthewp]

Great, thanks!