How zitadel/typescript works
Project Type and Purpose
• This is a Turborepo-powered monorepo containing:
• A full-stack Next.js application (apps/login) that implements a customizable ZITADEL login UI.
• Shared TypeScript packages (@zitadel/client, @zitadel/proto, config presets, ESLint/Prettier/Tailwind).
• An acceptance-test suite including mock Identity Providers (OIDC, SAML) and a “sink” service for email/SMS.
• Purpose: Enable you to develop, test, and ship a ZITADEL-compliant login UI with gRPC/Connect RPC, OIDC flows, MFA, SAML, OAuth, and more.
File Structure
• Top-level dirs
• apps/login: Next.js 13 app with App Router, UI pages, React components, server/edge functions.
• packages/*: Shared client libs, proto defs, config presets.
• acceptance: Docker/Go IDP mocks, Sink service, Playwright/Cypress test specs.
• CI/CD configs (.github/workflows), Docker files, Changesets, pnpm workspace, Turbo config.
• Architectural patterns
• Monorepo with Turborepo tasks and PNPM workspaces.
• Frontend SSR/ISR via Next.js, with serverless function endpoints under src/lib/server.
• Shared code layers: client abstraction (@zitadel/client), proto definitions, config layer.
• Acceptance environment orchestrated by Docker Compose, spinning up ZITADEL, mock providers, sink, and running end-to-end tests.
README for Additional Insights
• Confirms a “login UI” Next.js application using ZITADEL Session API and OIDC flows.
• Describes features: local registration, external IDPs, MFA factors, password flows, etc.
• Mentions tooling: gRPC stub generation (pnpm generate), local ZITADEL via Docker Compose (pnpm run-zitadel), acceptance sink (pnpm run-sink), tests (pnpm test:acceptance).