Auto-generated — not yet edited · only the numbers are verified
- TESIGN / RADAR
- REPOSITORY CARD
- lovablelabs/oj
lovablelabs/oj
An experimental Rust-native build tool for React apps.
RANKS Rising 7d #57
AT A GLANCE
- LANGUAGE
- Rust
- LICENSE
- MIT
- USAGE
- Use, change and redistribute, commercially too. Keep the notice.
- ACTIVITY
- last commit 2 days ago ()
- HOMEPAGE
- https://lovable.dev/blog/faster-previews-oj
- REPOSITORY
- GitHub ↗
- CATEGORY
- DEV TOOLS
A summary, not legal advice.
README EXCERPT
OJ OJ is a Rust-native build tool for React apps. It optimizes for memory and cold start, where running many builds (CI, agents, multi-tenant) under Vite gets expensive. OJ is meant to run real production React apps without changes to their source. Server rendering There is an SSR mode: oj dev --ssr src/entry-server.tsx in dev, and oj build --ssr for production. It streams the HTML out with renderToReadableStream instead of buffering, and the client hydrates through the normal dev pipeline, so Fast Refresh and HMR keep working over a server-rendered page. In dev the server modules run in a small persistent Node process (a module runner using vm.SourceTextModule ) that re-evaluates only what changed, instead of rebuilding a bundle per request. Plugins Vite/Rollup-style plugins run through a persistent Node plugin host. Drop an oj.plugins.mjs at the app root that default-exports a plugin array, or let oj read an app's vite.config.{ts,js,mjs} and pick up its plugins array directly. A TypeScript config (including one that imports local .ts files) is loaded via Vite's own config loader when Vite is installed, or bundled with the app's esbuild otherwise. From a vite.config oj also adopts…
The opening of the GitHub README as stored, at most 1,200 characters. Markdown is not rendered.
TIMELINE
- Repository created
- Last push
- FIRST SEEN BY TESIGN
AI chooses the lists under the owner’s delegation. No human review is running in September 2026. Total stars, increases, cross-source signals, last updates and licences are shown as evidence. How ranks work →
If this repository gets editorial text (why, build, who, start, caveat) it becomes an edited entry. Until then the page shows only stored GitHub metadata and numbers.