ReScript 12.0 ships a new build system. It is short. It is sharp. It aims to cut compile time and clean up the developer experience.
ReScript 12.0: New Build System, Faster Iterations, Clearer Errors
ReScript 12.0 ships a new build system. It is short. It is sharp. It aims to cut compile time and clean up the developer experience.
What changed
ReScript 12.0 introduces a rebuilt compilation pipeline. The focus is speed, more transparent error reporting, and a smoother feedback loop for incremental builds. The team rewired how files are tracked and how outputs are cached.
Performance gains you will notice
Incremental builds are faster. Recompiles touch fewer files. This matters when you work on large frontends. Faster builds mean faster feedback and less context switching.
Clearer error reporting
Errors are now clearer. Messages surface the root cause faster. The compiler points to the broken code with less noise. That reduces time spent hunting tiny mistakes.
How incremental builds and feedback loops improve
The new system narrows rebuilds to the minimum. You save minutes every day. That adds up. Quick builds keep focus. You ship more. You fix more.
Compatibility and tooling
The ReScript 12.0 build system aims to remain compatible with existing tooling. Most editors and language servers keep working. Some custom build setups may need tweaks. Tooling that assumed older cache layouts could require updates.
Migration considerations
Upgrading to ReScript 12.0 should be simple for most projects. But big, monorepo-style codebases may require careful testing. Expect these points:
- Validate incremental build times locally.
- Run CI builds end-to-end.
- Check any custom plugin or script that reads build artifacts.
My story: migrating a big repo
I once migrated a large UI repo at a company where I worked. I was Ermenildo Valdez Castro, Jr., then simply Ernie to my team. We had a tight release window. I remember a night in Seattle, coffee cold, terminal full of compile logs. We split the migration: one team tested local developer builds, another ran CI smoke tests. The new build system made local iterations fast. But one script in CI assumed the old cache layout and failed. We fixed it in a small patch. The fix took an hour. The faster local builds saved us days. That trade-off was worth it. 🛠️
Why this matters for type-safe frontend development
ReScript sits among modern compiler tools that prioritize developer velocity and correctness. Faster, clearer tools reduce friction for teams that build type-safe frontends. They make types useful in practice, not just in theory.
Where this fits in broader trends
Compilers are focusing on incremental work. Tooling like esbuild and incremental TypeScript changed expectations. ReScript 12.0 follows that path. The goal: less waiting, more doing.
Practical checklist before upgrading
- Run a full test suite in a feature branch.
- Validate editor and language-server behavior.
- Verify CI build artifacts and caching.
- Search for custom scripts that parse build outputs.
Final thoughts
ReScript 12.0 is practical. It tightens the developer feedback loop. It makes error messages clearer. It improves incremental build performance. For most teams, the benefits outweigh migration friction.
I write from years at big companies—Google, Microsoft, Amazon, and Zulily—and from nights fixing builds in Seattle. I am Ermenildo Castro. I have seen slow builds kill momentum. I have seen small fixes unlock weeks of work. Upgrade carefully. Test thoroughly. And enjoy the faster loop.
— Ermenildo V Castro (Ernie) 🇵🇭