Multi-Tenant Frontend Architecture with Nuxt.js
summary
A Nuxt monorepo powers multi-tenant SaaS using pnpm workspaces, Nuxt Layers, and a wrapped shadcn + CVA UI so tenants inherit base code but can override CVA functions; tenant-specific CVA configs merge with tailwind-merge so the tenant’s classes win. Deployments run from CI triggered by Git tag deployments to Firebase. The repo currently serves six brands and is designed to scale to ~30; a monorepo template lives on GitHub. Modularity (removing base modules) remains unsolved.
AI-written summary · about
chapters (9)
- 0:00Introduction and overview
- 3:02What is multi-tenancy
- 6:13Used tools and stack
- 8:40Architecture diagram explained
- 12:22Onion-layered architecture
- 13:03Theming with CVA and Tailwind
- 16:55Deployment strategy with Git tags
- 19:29Future improvements and challenges
- 21:12Summary and Q&A
related talks
35mA multisite Vue3 application for a multitenant enviromnent: a survival guide
37mBuilding Scalable Multi-Tenant Frontend Architecture for a B2B E-Commerce Platform
24mMulti-variant apps with Nuxt 3
22mDeep dive into Nuxt.js
26mLayers Unwrapped: A Fresh Approach to Nuxt App Architecture
21mHow to enable large scale collaboration between disciplines using Nuxt
38mLarge Scale Nuxt Architecture
43mScalable Multi-Tenant Frontend for an E-Commerce Platform
