Mako is Now Open Source

2024-06-28 by sorrycc

中文版: 《Mako 开源了》

Hi, I am sorrycc, one of the main maintainers of Mako, and also the creator of Umi, Dva, Father, and other libraries. I am thrilled to announce that Mako is finally open source, the Github url is , and I’m excited to formally introduce it to you today.

What is Mako?

Mako is an “extremely fast” and “production-grade” front-end build tool, based on Rust.

The “extremely fast” aspect was our initial motivation for starting the Mako project. Without build speed issues, Mako would not have been necessary. Refer to the Benchmark section below for some data, and we are constantly exploring even faster build speed solutions. The “production-grade” label comes from the fact that since 2023.11.24, Mako has been officially released internally at Ant Group. It has been validated with engineering practices on thousands of projects and all used npm packages and their versions. It has been implemented in hundreds of projects, serving various platforms and business scenarios internally, including management backends, mini-programs, H5 mobile, low-code, marketing, component libraries, component packaging, Serverless Functions, etc., demonstrating fully production-grade capabilities.

You can visit to learn more about Mako’s features.

How did Mako come about?

Last year (2023.3), our team launched 3 projects, Rust, SSR, and AIG, and we took on the Rust direction to tackle build performance issues. Our team has been exploring faster build speed solutions, including MFSU, which optimizes build speed within Webpack. However, this had certain limitations. We sought a thorough solution through Rust.

You might wonder why we didn’t use existing Rust tools but decided to create one ourselves. The reasons are complex. For instance, 1) the maturity level of community libraries and their compatibility with Ant’s needs, we researched all the community Rust build solutions before starting, ultimately deciding on creating our own, 2) having control, due to business reasons, build tools at Ant require a lot of customization, and this proved true as we found many matching needs after internal release, 3) the modern meta-frameworks require compilation-time frameworks, in addition to build, they also have a lot of compilation needs, especially in SSR & RSC scenarios, for example, RSC scenarios required 4 builds internally, 4) the need to learn Rust and for team growth, modern frontend tools are all written in Rust, and we would fall behind if we did not advance.

The timeline above is for Mako. Mako kicked off in 2023.3, had its first usable version by 2023.7, was internally released at Ant in 2023.11, and was open-sourced by 2024.6. We initially had 3 members with zero Rust experience, with team members, especially the virtual team, coming and going, learning Rust while digesting build knowledge and working on Mako was challenging, but fortunately, we succeeded and learned a lot in the process. We would like to thank the pioneers in the build domain like Webpack, Farm, and Rspack, as well as ChatGPT.


Mako has put a lot of effort into speed. Below is some Benchmark data.

The Benchmark ran on a project that Turbopack also tests, on a Mac Book Pro M2 Max. It includes dimensions such as dev cold start time, root node and leaf node HMR time, production Build build time, and JS bundle size. (Note: Farm was not tried successfully using API mode, so no HMR data was generated; RsBuild had some issues upgrading to 0.7, so it’s still on 0.6 for now. RsBuild 0.7 might be a bit faster.)

If you’re interested, feel free to clone the repository and try it out yourself.

$ git clone
$ cd benchmark
$ pnpm i
$ pnpm run setup
$ pnpm benchmark

Here’s how we compare to our previous selves.

For Ant Design Pro full project build, Webpack takes 16s, Mako takes 3.9s, a 4x speed improvement.

For Ant Design Pro full project build, Mako is almost always real-time hot updates.

Intranet Hybrid framework Smallfish project build, based on RSC (React Server Components), scaffold project, build time reduced from 36.7s to 1.2s. It looks a bit exaggerated, but these are real data.

These are more examples of speed improvements on such RSC projects.

Additionally, Mako also has an experimental SSU feature, similar to the previous MFSU implementation, which does packaging and caching of dependencies. Depending on the ratio of source code to dependencies, it can achieve a 10-50x speed boost in Dev hot start-up. Currently, it can be enabled with the SSU=true environment variable.

How to participate?

If you want to experience Mako, you can create a Mako + React project with a single command using the scaffolding tool.

$ npm create mako

If you’re a Umi user, it’s very simple to experience Mako!

# Make sure your version is 4.2.0 or above
$ npx umi -v
# Enable Mako configuration
$ npx umi config set mako {}
# Run build or other commands
$ npx umi build

If you want to discuss issues or suggestions about Mako, you can scan the QR code to join our WeChat group. (If it’s expired or the group is full, please go to for a new QR code.)

Or click the following link to join our Telegram group.

Also, you’re welcome to subscribe to Mako updates via RSS. We’ll post the latest news about Mako and high-quality technical articles related to building.

If you want to get involved in Mako’s open source, you can visit and CONTRIBUTING document to learn more. Anyone who has submitted Bugfix or Feature PRs can choose to join Mako’s developer DingTalk group.

If you plan to deeply promote and apply Mako in your company, or develop based on Mako, you can contact us ( for discussion. We can provide the relevant training, consulting, and more timely support services.

Live Q&A

Tonight (June 28, 2024) at 9 PM, we’ll be hosting a live Q&A on Bilibili, reservation link available at We welcome everyone to participate, and you can ask anything about Mako. If you have questions about Mako, you can fill in the questionnaire in advance at


The release of Mako would not have been possible without each contributor, especially since most of them have participated in their spare time. Thank you!

And many authors of the community’s dependencies libraries!

Edit this page on GitHub