Proposal: Official Monorepo Support for Vue (Inspired by NestJS)

[Trandx]

Hello 👋,

More and more teams are using Vue in monorepo setups: design systems, shared UI libraries, multiple applications, and internal packages.
While Vue works very well in monorepos today, there is no official, Vue-endorsed structure or convention.

---

🎯 The Problem

In real-world Vue monorepos, teams often have to:

• Duplicate Vite and TypeScript configurations
• Manually manage path aliases across packages
• Handle partial builds and dependency graphs themselves
• Generate and align .d.ts files manually
• Maintain inconsistent project structures across teams

This leads to:

• Fragmentation in the ecosystem
• Inconsistent developer experience
• Higher onboarding and maintenance costs

---

💡 The Proposal

Introduce an official, optional monorepo convention for Vue, similar in spirit (not implementation) to what NestJS provides with nest-cli.json.

This could include:

• A simple config file (e.g. vue-monorepo.json)
• Recommended conventions for apps/ and packages/
• First-class integration with Vite, TypeScript, and pnpm
• CLI-level support for common tasks (targeted build, watch, type generation)

⚠️ This would be fully opt-in and non-prescriptive.

---

🚀 Benefits for the Vue Ecosystem

• A consistent monorepo experience across Vue projects
• Easier creation and maintenance of shared Vue libraries
• Better DX for design systems and internal tooling
• Reduced configuration duplication
• Stronger enterprise adoption without sacrificing simplicity

This is not meant to replace existing tools like Nx, Turborepo, or pnpm workspaces, but rather to provide a Vue-first baseline that integrates cleanly with them.

Thanks for your time, and thanks for building Vue 🙏

[lizhan12]

这是来自QQ邮箱的自动回复邮件。 我已经收到了你的来信，我会尽快回复。