🦀 @rspack_dev contributor, maintaining Rspress https://teapawt.net/t.co/FM70CCzm6A 😁 Error Translation Engineer 🔨 Monorepo & Build tooling
Hangzhou
Joined January 2022
- Tweets2.8K
- Following630
- Followers2K
- Likes14.6K
Introducing SWC Next: the foundation for SWC’s next major version, built on a new architecture inspired by Yuku.
- Up to 3x faster native parsing
- Up to 10x faster parsing through the JavaScript API
- A flat, ESTree-based AST designed for speed, memory efficiency, and JavaScript extensibility
Starting with parsing, we’re bringing the rest of SWC to this new architecture.
Built together by the SWC and Rstack teams.
Submit this bench data to the upstream
github.com/yuku-toolchain/ec…
Soon retweeted
SWC Next is here!
Today, customizing how your code is transformed often means using Babel plugins or writing Wasm plugins for SWC.
I believe the next generation of JS compilers should combine Rust's performance with the flexibility to write custom transform plugins in JavaScript.
SWC Next's flat AST enables efficient data exchange between Rust and JS, laying the groundwork for fast JS plugins 🚀
Introducing SWC Next: the foundation for SWC’s next major version, built on a new architecture inspired by Yuku.
- Up to 3x faster native parsing
- Up to 10x faster parsing through the JavaScript API
- A flat, ESTree-based AST designed for speed, memory efficiency, and JavaScript extensibility
Starting with parsing, we’re bringing the rest of SWC to this new architecture.
Built together by the SWC and Rstack teams.
QuickJS -> QuickRs
New from PocketJS: quickjs-oxide.
A JavaScript interpreter modeled after QuickJS, implemented from scratch by AI in Rust with zero unsafe code, and the first of its kind to achieve performance competitive with the original QuickJS.
We spent one month achieving a high Test262 pass rate, then another month cleaning up the code, getting rid of the AI slop, and reaching competitive performance with just a stack VM and reference counting. Over the last weekend at RustChinaConf, we rewrote the core into a register VM and achieved this level of performance in just two days.
Now quickjs-oxide outperforms most non-JIT JavaScript engines on benchmarks like V8 v7 and the Octane suite, using only around 30% more memory than QuickJS, while maintaining zero lines of unsafe implementation code and no external dependencies except for BigInt support.
Huge credit to @ericoolen_eric for making this happen, and massive thanks to our sponsor @ZephyrCloudIO for supporting the journey!
Soon retweeted
We moved the Zephyr Cloud dashboard (1 host + 7 Module Federation remotes) from Rspack to Rsbuild 2 by @rspack_dev, then let Rsdoctor 2 drive the cleanup.
First load: 1,045 → 729 KB gzip (−30%)
Build: 112s → 90s (−20%)
15-route journey: 1,294 → 788 KB (−39%)
Numbers 🧵
Soon retweeted
TanStack CLI now supports Rsbuild! 🦀
Create your next TanStack app with:
npx @tanstack/cli create my-app
Select React → Rsbuild, and start building.
If I were an official TypeScript developer, I'd feel a lot of pressure - the entire community wants to replace me instead of helping me get better
Soon retweeted
Just open-sourced Frametell 🎬
Turn your ideas, notes into narrated explainer videos. An AI director agent plans the storyboard, writes the script, voices it and animates every page.
One sentence in, a 1080p film out.
github.com/sitor-ai/frametel…
Watch it turn one sentence into a film, start to finish 👇
Soon retweeted
The @ZephyrCloudIO docs have a new version 🪐
New landing page, plus one command to let coding agents use, promote and roll back your deployments.
docs.zephyr-cloud.io
这是我在算法可视化的一次尝试 （with AI）
1. 底层字幕解说
2. svg 凹动画
3. real-world case
4. 一点点 human-in-the-loop + 个人偏好
🙌欢迎观感反馈～帮助我做的更好
Soon retweeted
一旦トップページのデザインが完成したので公開した
あとでドキュメント周りも見直す予定
praha-inc.github.io/byethrow…
Soon retweeted
What’s less widely known is that many large companies, including Microsoft and Canva, maintain their own internal versions of Rspack built on top of Rspack’s Rust API, allowing them to meet highly customized internal requirements and push performance even further.
While this is not particularly friendly to Rspack’s download numbers, it is something we very much welcome. In fact, we created rspack-binding-template specifically to reduce the maintenance burden of maintaining an Rspack fork.
We have similar practices internally as well, so we fully understand why teams choose this approach. Ultimately, what matters most to us is whether Rspack can meet users’ real-world needs—not whether we can maximize the apparent impact or adoption metrics of our own tooling.
