Skip to content
Back to skills

Angular Upgrade Modules Angular V21 Ngmodulefactory Removal

ASecurity

Remove Angular NgModuleFactory usage after an Angular 21 upgrade when dynamic module loading, plugin systems, or legacy loaders still depend on NgModuleFactory. Use when replacing factory-based module creation with supported APIs.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 2, 2026
developmenttypescriptgoangularapi

Works with

  • api

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill angular--upgrade--modules--angular-v21-ngmodulefactory-removal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Angular Upgrade Modules Angular V21 Ngmodulefactory Removal?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Angular  Upgrade  Modules  Angular V21 Ngmodulefactory Removal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-angular-upgrade-modules-angular-v21-ngmodulefactor/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-angular-upgrade-modules-angular-v21-ngmodulefactor)

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

Download with Pro
SKILL.md
---
id: angular.upgrade.modules.angular-v21-ngmodulefactory-removal
name: Angular v21 NgModuleFactory Removal
description: >
  Remove Angular NgModuleFactory usage after an Angular 21 upgrade when dynamic module loading, plugin systems, or legacy loaders still depend on NgModuleFactory. Use when replacing factory-based module creation with supported APIs.
stack:
  - Angular
  - TypeScript
category: modules
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - NgModuleFactory
  - dynamic module loading
  - legacy loaders
  - plugin systems
compatibility:
  angular:
    min: "21"
---

# Angular v21 NgModuleFactory Removal

## Purpose

Remove Angular NgModuleFactory usage after Angular 21.

## When to Use

- The app dynamically loads modules.
- The app uses legacy plugin loaders or factory-based module creation.

## When Not to Use

- The app does not use NgModuleFactory.
- The app is still in a version hop.

## Required Inputs

- dynamic module loading code
- plugin loaders
- legacy factories

## Procedure

1. Find NgModuleFactory usage.
2. Replace with supported APIs.
3. Validate dynamic loading behavior.

## Do

- Keep dynamic loading explicit.
- Validate plugin and module loading.

## Do Not

- Do not keep NgModuleFactory.
- Do not mix this with the version hop.

## Review Checklist

- [ ] NgModuleFactory usage is removed.
- [ ] Dynamic loading works.
- [ ] Tests pass.

## Expected Output

1. Dynamic module summary.
2. API replacement summary.
3. Test result.

## Exit Criteria

- NgModuleFactory risk is explicit.

Attribution

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

Loading comments…