Ecosystem: Utoo , Dev Tools & Bundling for react app

[xusd320]

Library Name

Utoo

Repository URL

https://github.com/utooland/utoo

Why should this be included?

Utoo and Ant Design belong to the same team. Utoo provides an npm-compatible package manager, a Turbopack-based build tool, and a complete frontend development toolchain capable of running directly in the browser. Additionally, Utoo maintains friendly collaboration and communication with the Next.js upstream community.

Evidence of React ecosystem relevance

1. natively react support : https://utoo.land/en/docs/utoopack/config#react
2. in-browser toolchain, directly install deps, building react app with postcss and tailwindcss support: https://utoo-repl.vercel.app/
3. contributions to next.js and Turbopack: https://github.com/search?q=repo%3Avercel%2Fnext.js%20is%3Apr%20is%3Amerged%20author%3Afireairforce%20author%3Axusd320&type=pullrequests

Non-goals

No response

[dougbot-agent]

Thanks for opening this — I want to make sure we fully understand the expected behavior before we add it to the tracked ecosystem.

A few questions:

1. For RIS/data collection, which package should be treated as the canonical package mapping for this repo: utoo, @utoo/pack, @utoo/web, or something else?
2. Should inclusion here mean tracking the whole utooland/utoo toolchain as one ecosystem entry, or specifically the React-facing bundling/dev-tool surface?
3. Once included, should this appear only in the tracked libraries/directory + RIS scoring pipeline, or are there any other pages/comparison buckets you expect it to show up in?

If possible, a minimal repro or screenshot would help a lot.

From the repo README it looks like there are multiple npm packages under one repository, so I’m tagging @sethwebster for maintainer/product guidance on the canonical scope and package mapping before implementation.

[sethwebster]

At this point, I'm not sure that Utoo would qualify as highly leveraged in the React ecosystem. The libraries / frameworks support is to be applied toward libraries that have significant adoption and usage across the community. It seems Ant Design does meet that threshold but does Utoo?

[dougbot-agent]

Thanks for the added context. To move this forward, we need a bit more evidence that Utoo clears the bar for broad React ecosystem leverage.

A few questions:

1. Do you have adoption signals we should weigh here for the React-facing surface specifically (for example npm download numbers, active users, or notable production usage)?
2. Are there concrete examples of React apps, libraries, or teams using Utoo in production today?
3. Which single package/surface should we evaluate as the canonical entry for this request: utoo, @utoo/pack, @utoo/web, or something else?

If possible, links to usage examples, package pages, or screenshots would help a lot. That will make it easier to evaluate whether this should be tracked and, if so, exactly what should be included.

[dougbot-agent]

Following up here since this has been quiet for a bit.

We're still blocked on two things before this can move out of status:needs-info:

1. evidence that the React-facing Utoo surface has meaningful ecosystem adoption/leverage
2. the single canonical package/surface we should evaluate for tracking (utoo, @utoo/pack, @utoo/web, or another package)

If you can share package-level adoption signals, production usage examples, or the exact package/surface you want evaluated, we can take another pass.

[xusd320]

Thank you very much for your reply. I sincerely apologize for the delayed response; I was tied up with other commitments recently and unfortunately missed the GitHub notifications.

To provide clearer context regarding the utooland/utoo project, I would like to highlight a few key details:

1. utoo bin: This is a general-purpose package manager and operates independently of the React ecosystem.
2. @utoo/pack and @utoo/web: These packages are deeply integrated into Ant Group's internal technology stack, as well as its open-source ecosystem (including umi and dumi). This extends to the antd project itself; in fact, the official antd documentation site is built using @utoo/pack. Furthermore, @utoo/web primarily powers various browser-based "vibe coding" products, offering zero-server-overhead project building and preview capabilities. These types of tools are widespread across Ant Group and Alibaba, and crucially, all of them are built entirely on React.
3. Community Adoption: While @utoo/pack and @utoo/web provide React projects with out-of-the-box build capabilities and seamless compatibility with most Webpack features, I want to be transparent that they are not yet widely adopted across the broader open-source community. The decision to adopt these tools ultimately rests with individual developers, and we are still in the process of growing our community presence.

From a technical perspective, I believe @utoo/web introduces a novel approach to React application development. It shares its core architecture with @utoo/pack but is compiled to WebAssembly. This means it requires zero local environment dependencies and works natively within the browser out of the box. We are also actively exploring porting the React Compiler to Wasm for this environment, which would allow developers to leverage the compiler's capabilities directly in their browsers.

I would be incredibly grateful for any guidance or support in helping the broader React community discover this innovative technology. I completely understand that any decisions regarding official ecosystem recognition ultimately rest with the React Foundation's leadership.

Thank you again for your time and consideration.

[dougbot-agent]

Thanks — this clarification helps.

The scope is clearer now: the React-facing surfaces here are @utoo/pack and @utoo/web, while utoo bin itself is not the part we would evaluate for React ecosystem tracking.

The main remaining question is maintainership/product threshold rather than package mapping: your note confirms these tools are used heavily inside Ant Group / Alibaba, but are not yet broadly adopted across the wider open-source React ecosystem. Keeping this in status:needs-info for now because we still need a maintainer call on whether that internal leverage is sufficient for inclusion.

@sethwebster could you take a final pass on whether this clears the bar for tracked ecosystem inclusion, or should stay out until there is stronger public/community adoption evidence?

[dougbot-agent]

Thanks for the additional detail — the package scope is clearer now.

At this point the remaining blocker is a maintainer/product decision, not missing reporter detail:

• React-facing scope appears to be @utoo/pack and @utoo/web
• the open question is whether strong internal Ant Group / Alibaba usage, without broader public ecosystem adoption yet, is enough for tracked inclusion here

Marking this as status:blocked while we wait on that threshold call.

@sethwebster could you make the inclusion call on whether this should be tracked now, or held until there is stronger public/community adoption evidence?

[sethwebster]

@xusd320 Thanks for the clarity. As a foundation, we are working to be as supportive and inclusive as possible while also being intentional about the scope of our support; there are simply too many packages to support to support them all meaningfully.

At this time, I don't think we can include @utoo/pack / @utoo.web but I do encourage of course the continued focus and work to grow the community and adoption. I love that there is innovation going on in this space, and have found its best to let our community put its finger on the scale when new approaches are better than what we already have.

I encourage content to help people understand what is on offer and what makes this approach better than what we already have; showcase what people are building, what new capabilities are unlocked, etc.