Angular Build Angular V22 Build System Migration

Name: Angular Build Angular V22 Build System Migration
Author: janpereira-dev

ASecurity

Use this skill when Angular 22 build, serve, or test infrastructure needs to move away from deprecated builder paths.

4 stars

0 votes

0 copies

0 views

Added 10/2/2026

developmenttypescriptgoangular

Works with

cli

Security Analysis

A100/100

Scanned 10/2/2026

npx -y skills add janpereira-dev/ngAutoPilot --skill angular--build--angular-v22-build-system-migration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Angular Build Angular V22 Build System Migration?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Angular Build Angular V22 Build System Migration

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-angular-build-angular-v22-build-system-migration/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-angular-build-angular-v22-build-system-migration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

Files

SKILL.md

---
id: angular.build.angular-v22-build-system-migration
name: Angular v22 Build System Migration
description: >
  Use this skill when Angular 22 build, serve, or test infrastructure needs to move away from deprecated builder paths.
stack:
  - Angular
  - TypeScript
category: build
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - build system
  - "@angular/build"
  - webpack builders
  - architect
  - ng serve
compatibility:
  angular:
    min: "22"
---

# Angular v22 Build System Migration

## Purpose

Use this skill when Angular 22 build, serve, or test infrastructure needs to move away from deprecated builder paths.

## When to Use

Use this skill when:

- The app still depends on webpack-based Angular builders.
- CI or local commands need a v22-compatible build path.
- The project has custom builders or architect wiring that may need a rewrite.

## When Not to Use

Do not use this skill when:

- The issue is only source code and not the build pipeline.
- The project already uses the new build path cleanly.
- A narrower CLI or workspace migration skill is a better fit.

## Required Inputs

- angular.json
- build and serve scripts
- CI commands
- custom builders

## Procedure

1. Map the old build targets to the supported v22 builder path.
2. Check custom architect or CLI wiring for removed packages.
3. Validate local serve behavior, including the effective port source.

## Do

- Keep the migration incremental.
- Prefer the supported builder path over deprecated webpack builders.
- Verify the same behavior in CI and locally.

## Do Not

- Do not keep deprecated builder aliases in new config.
- Do not assume custom CLI glue survives unchanged.
- Do not let the build migration spill into source refactors.

## Review Checklist

- [ ] The build target uses the supported v22 path.
- [ ] CI and local runs still work.
- [ ] Any removed CLI entry points were addressed.

## Expected Output

1. A build-migration summary.
2. The updated builder path.
3. Any remaining CI or CLI risks.

Attribution

janpereira-dev

View source See grades on GitHub More from janpereira-dev →

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

--- id: angular.build.angular-v22-build-system-migration name: Angular v22 Build System Migration description: > Use this skill when Angular 22 build, serve, or test infrastructure needs to move away from deprecated builder paths. stack: - Angular - TypeScript category: build status: stable version: 0.10.0 owner: NgAutoPilot triggers: - build system - "@angular/build" - webpack builders - architect - ng serve compatibility: angular: min: "22" --- # Angular v22 Build System Migration ## Purpose Use this skill when Angular 22 build, serve, or test infrastructure needs to move away from deprecated builder paths. ## When to Use Use this skill when: - The app still depends on webpack-based Angular builders. - CI or local commands need a v22-compatible build path. - The project has custom builders or architect wiring that may need a rewrite. ## When Not to Use Do not use this skill when: - The issue is only source code and not the build pipeline. - The project already uses the new build path cleanly. - A narrower CLI or workspace migration skill is a better fit. ## Required Inputs - angular.json - build and serve scripts - CI commands - custom builders ## Procedure 1. Map the old build targets to the supported v22 builder path. 2. Check custom architect or CLI wiring for removed packages. 3. Validate local serve behavior, including the effective port source. ## Do - Keep the migration incremental. - Prefer the supported builder path over deprecated webpack builders. - Verify the same behavior in CI and locally. ## Do Not - Do not keep deprecated builder aliases in new config. - Do not assume custom CLI glue survives unchanged. - Do not let the build migration spill into source refactors. ## Review Checklist - [ ] The build target uses the supported v22 path. - [ ] CI and local runs still work. - [ ] Any removed CLI entry points were addressed. ## Expected Output 1. A build-migration summary. 2. The updated builder path. 3. Any remaining CI or CLI risks.