Angular Rspack

Experimental Angular builders for running applications with Rspack and extending the generated Rspack configuration.

The current work consolidates the native Rspack implementation into @twig-it/angular-rspack. The builder is not yet a drop-in replacement for every Angular application option; its supported surface and known limitations are documented explicitly.

Current scope

• Application builds powered directly by Rspack
• Development server with watch mode and live reload
• Custom Rspack configuration merging
• Angular CLI 20 compatibility
• A sanity application for build and development-server verification

See the angular-rspack package documentation for installation and usage, and the supported-features matrix for the compatibility contract.

Workspace

• packages/angular-rspack — builder implementation
• packages/angular-rsbuild — Rsbuild builder implementation
• packages/angular-rstest — Rstest integration
• examples/angular-rspack/sanity-app — integration example
• examples/angular-rsbuild/sanity-app — Rsbuild integration example

Builders and Angular must use matching major versions. The current workspace targets Angular CLI 20.

Development

yarn install
yarn sanity

The repository-wide sanity command removes generated outputs, builds all three publishable packages and every Rspack/Rsbuild example, and then runs package tests, pack checks, example smoke tests, Rstest jsdom/happy-dom/Chromium tests, coverage checks, watch-mode smoke tests, and the Rsbuild MFE Playwright test.

The phases can also be run independently:

yarn clean
yarn build:all
yarn test:all

GitHub Actions uses production/headless variants that exclude the interactive watch smoke test:

yarn build:all:ci
yarn test:all:ci

Install Chromium before the first complete local test run:

yarn playwright install chromium

For focused Angular Rspack development:

yarn workspace @twig-it/angular-rspack build
yarn workspace @twig-it/angular-rspack test

Status

This project is experimental. Review the supported-features matrix before adopting it in an application, especially if the application relies on advanced Angular build options, server-side rendering, internationalization, or service workers.