I’ve thrown a modified t3code and pretty much every frontier model working in tandem over multiple subaccounts on a relatively “low-hanging fruit” for rspack— a portable cache that’s worktree-aware. While this doesn’t solve the memory challenges exceptionally, it does have a significant impact on agentic development. The question came from Copilot: “If 80% of the code isn’t changing, why can’t the compiler share memory when working concurrently in worktrees?”View quoted post on X
Ultimately, that’s a large architectural change for rspack to just try, especially given the tools’ reliance in trillion-dollar companies, and our own company too.
The path of least resistance would be making the cache portable; from there, the option to think about how to optimize or shift rye architecture could be somewhat explored, while providing users today with gains specifically targeting machine contention.
I’ve been testing this using @grafana @gitlab @sentry codebases, which consume rspack already and are the general target market for large, complex, enterprise-style builds.
If you are on the main worktree and create a new one, the rspack dev server, when you change a module, will only HMR one module. The warm vs. cold initial builds and hmr cycles were pretty substantial. If that agent decides to split work and makes a new worktree, rspack will rebase the cache off the base worktree, not the main one. I tested this up to 6 worktrees deep.
One prominent challenge: loaders often use require.resolve or dirname, or import.meta to resolve an absolute path to a resource. In Vue loader and React transforms, this would cause the loader to rerun on a worktree. Like gitlab it cost 16k modules to be rebuilt. Finding a solution to rebasing absolute paths in worktrees was tricky. Also, you have to ensure things like the time it takes to replicate the cache (use reflink or cow) isn’t longer than rspack just rawdogging it.
Introducing tsrs: a Rust port of the TypeScript compiler 🦀View quoted post on X
We are not forking TypeScript!
◆ In close collaborating with the TypeScript team
◆ Up to 8x faster than TS 7.0 & ~70% less memory
◆ Runs in WASM, so it works in your browser & on Workers
◆ Soon part of the Oxc toolchain
npx tsrs
blog.cloudflare.com/typescript-rus…
Announcing tsc-rs (aka ts-rust), my complete rewrite of the Typescript compiler, type checker, and LSP, all in Rust.
This is a project I've had agents working on for 5 months now. I burned ~$400k of Codex tokens and got nowhere. Burned ~$20k of Opus and got there in 2 weeks.
I have not read a single line of the code.
tsc-rs is an open source drop-in replacement for tsc, and it's available now.View quoted post on X
