IdeaWell

Project ideas from Hacker News discussions.

The Rust React Compiler is now native in Vite

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Major speed improvements by swapping Babel for Rust‑based transformers
- “No more babel in my compilation pipeline, yay!” – adzm
- “Time from npm run dev to ready went from 6 to 2 seconds.” – adzm (after switching)
- “Compiling at work took a minute for full builds with babel, and with rsbuild it now takes about 0.9 seconds.” – Waterluvian
- “OXC Transformers are amazingly faster than Babel… It's still very early but it's plenty, plenty fast.” – vmsp

2. Questions about compatibility with existing toolchains (React Compiler, Next.js, Vite, etc.)
- “Does this work with reacts fancy new compiler that is meant to optimize away various hooks?” – syspec
- “Why does the Nextjs version of React compiler require a babel plugin when the vite version doesn't need it? Next.js is on SWC, not sure why they need a babel plugin.” – Onavo
- “Because it isn't supported by SWC yet.” – mexicocitinluez

3. Enthusiastic adoption and real‑world success with minimal configuration effort
- “Literally just did the config changes in the article, no issues.” – adzm
- “If it wasn't obvious from the article, this is an implementation in the same thing in rust, ergo significantly faster.” – ownagefool
- “I'm building a framework … fully backed by OXC and Vite.” – vmsp
- “Because next is the worsttttt” – crypto137 (humorous endorsement of moving away from Next.js/Babel)

🚀 Project Ideas

Next-OXC Plugin

Summary

  • A zero‑config Next.js plugin that replaces the required Babel plugin with OXC‑based JavaScript/TypeScript transforms, removing Babel from the build pipeline.
  • Core value proposition: Cut Next.js dev‑server start‑up and hot‑reload times from seconds to sub‑second by leveraging OXC’s Rust speed.

Details

Key Value
Target Audience Next.js developers who want faster builds and dislike Babel overhead
Core Feature Drop‑in next.config.js plugin that wires OXC parser/transformer into Next.js’s SWC pipeline, bypassing Babel entirely
- Tech Stack Rust (OXC compiled to WASM or native via oxc_wasm), Node.js plugin, SWC hook interface
Difficulty Medium
Monetization Hobby

Notes

  • HN users complained: “Why does the Nextjs version of React compiler require a babel plugin when the vite version doesn't need it?” – this plugin would eliminate that need.
  • Enables discussion around integrating Rust toolchains into mainstream React frameworks and could become a community‑maintained alternative to the official Babel plugin.

Metro-OXC Loader

Summary

  • A Metro bundler loader that uses OXC to transform JS/TS and CSS‑in‑JS (e.g., StyleX) instead of Babel, targeting React Native projects.
  • Core value proposition: Significantly reduce Metro build times and eliminate Babel‑related config friction for mobile developers.

Details

Key Value
Target Audience React Native developers using Metro who want faster iteration and less Babel complexity
Core Feature Loader that intercepts .js/.ts/.jsx/.tsx files and delegates parsing/transforming to OXC, optionally handling StyleX syntax
Tech Stack Rust (OXC) exposed via a Node.js native addon or WASM, Metro custom loader interface
Difficulty Medium
Monetization Hobby

Notes

  • VMsp noted: “Instead of Metro (React Native's bundler), which also uses Babel, it's just Vite… still very early but it's plenty, plenty fast.” This loader would bring that speed to Metro.
  • Provides a concrete upgrade path for teams stuck with Babel‑heavy Metro configs, sparking discussion about Rust‑based tooling in mobile stacks.

OXC Cache Service

Summary

  • A distributed cache service that stores OXC transformation AST/bytecode results, allowing developers and CI pipelines to reuse previous builds and achieve near‑instant incremental compiles.
  • Core value proposition: Turn OXC’s already fast transforms into a shared, persistent cache that cuts redundant work across machines and branches.

Details

Key Value
Target Audience Frontend teams using OXC‑based tooling (Vite, Next.js plugins, Metro loader, etc.) who run frequent builds in CI and locally
Core Feature HTTP/gRPC API + CLI wrapper that computes a hash of source + OXC version, stores/retrieves transformed output; supports LRU, TTL, and private/public buckets
Tech Stack Rust backend (Actix-web or Tokio), S3-compatible storage or Redis, optional WASM API gateway
Difficulty High
Monetization Revenue-ready: Usage-based SaaS (e.g., $0.10 per GB‑month stored + $0.01 per million cache lookups)

Notes

  • HN users praised OXC speed: “Time from npm run dev to ready went from 6 to 2 seconds.” A cache would push that even lower, especially in CI where repeats are common.
  • Encourages discussion about build‑artifact sharing, reproducibility, and the potential for a universal OXC cache akin to sccache for Rust compilation.

Read Later