mirror of https://github.com/zitadel/zitadel.git synced 2026-07-25 18:28:00 +00:00

Files

T

Wim Van LaerandGitHub 699ed17918 chore: rename configuration to settings (#11568 )

# Which Problems Are Solved

naming inconsistencies: Configuration <-> Settings

# How the Problems Are Solved


# Additional Changes


# Additional Context

- Closes #11282

2026-02-18 14:25:42 +01:00

3.1 KiB

Raw Permalink Blame History

Zitadel Management Console

The Management Console is Zitadel's management UI.

It is built using Angular and part of the Zitadel monorepo.

To get started follow the contributing quick start.

Building

To build for production:

pnpm nx run @zitadel/console:build

This will:

Generate proto files (via prebuild script)
Build the Angular app with production optimizations

Linting

To run linting and formatting checks:

pnpm nx @zitadel/console:lint

To auto-fix formatting issues:

pnpm nx @zitadel/console:lint-fix

Project Structure

src/app/proto/generated/ - Generated proto files (Angular-specific format)
buf.gen.yaml - Local proto generation configuration
project.json - Nx orchestration and caching for builds and tests
prebuild.development.js - Development environment settings script

Dependency Chain

The Management Console app has the following build dependencies managed by Nx:

@zitadel/proto:generate - Generates the protobuf stubs
@zitadel/client:build - Builds the TypeScript gRPC client library
@zitadel/console:generate - Generates Management Console-specific protobuf stubs
@zitadel/console:build - Creates a production build from Management Console

This ensures that the Management Console always has access to the latest client library and protobuf definitions.

Proto Generation Details

@zitadel/proto generation: Modern ES modules with @bufbuild/protobuf for v2 APIs
Local buf.gen.yaml generation: Traditional protobuf JavaScript classes for v1 APIs

The Management Console app calls Zitadel v1 and v2 APIs. As long as the Management Console still calls v1 APIs, it needs to import client stubs from separate sources:

Source outputs from direct buf generation for v1 APIs
@zitadel/client for v2 APIs

Legacy v1 API (Traditional Protobuf)

Uses local buf.gen.yaml configuration
Generates traditional Google protobuf JavaScript classes extending jspb.Message
Uses plugins: protocolbuffers/js, grpc/web, grpc-ecosystem/openapiv2
Output: src/app/proto/generated/
Used for: Most existing Management Console functionality

Modern v2 API (ES Modules)

Uses @zitadel/proto package generation
Generates modern ES modules with @bufbuild/protobuf
Uses plugin: @bufbuild/es with ES modules and JSON types
Output: login/packages/zitadel-proto/
Used for: New user v2 API and services

Dependency Management

The Management Console's project.json ensures proper execution order:

@zitadel/proto:generate runs first (modern ES modules)
Management Console's local generation runs second (traditional protobuf)
Build/lint/start tasks depend on both generations being complete

This approach allows the Management Console app to use both v1 and v2 APIs while maintaining proper build dependencies.

Legacy Information

This project was originally generated with Angular CLI version 8.3.20 and has been updated over time.

3.1 KiB Raw Permalink Blame History