Skip to content
Back to skills

Angular Upgrade Router Angular V14 Router Resolver First Emission

ASecurity

Review router resolvers for first-emission behavior before or during Angular 14 migration. Use when multi-emission observables or delayed resolver completion affect navigation.

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

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill angular--upgrade--router--angular-v14-router-resolver-first-emission --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Angular Upgrade Router Angular V14 Router Resolver First Emission?

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

Security grade badge for Angular  Upgrade  Router  Angular V14 Router Resolver First Emission
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-angular-upgrade-router-angular-v14-router-resolver/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-angular-upgrade-router-angular-v14-router-resolver)

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.router.angular-v14-router-resolver-first-emission
name: Angular v14 Router Resolver First Emission
description: >
  Review router resolvers for first-emission behavior before or during Angular 14 migration. Use when multi-emission observables or delayed resolver completion affect navigation.
stack:
  - Angular
  - TypeScript
category: router
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - resolver first emission
  - router resolver
  - navigation completion
compatibility:
  angular:
    min: "14"
---

# Angular v14 Router Resolver First Emission

## Purpose

Review resolver completion behavior.

## When to Use

- Router resolvers may emit more than once.
- Navigation depends on first-emission assumptions.

## When Not to Use

- Resolvers are already single-emission.
- The app has no resolver logic.

## Required Inputs

- resolver code
- route config
- navigation tests

## Procedure

1. Identify multi-emission resolvers.
2. Ensure navigation only relies on the intended emission.
3. Validate routing behavior.

## Do

- Keep resolver contracts explicit.
- Validate navigation completion.

## Do Not

- Do not assume multi-emission timing is harmless.

## Review Checklist

- [ ] Resolver behavior reviewed.
- [ ] Navigation tests updated.
- [ ] No unintended emissions remain.

## Expected Output

1. Resolver behavior summary.
2. Test notes.

## Exit Criteria

- Resolver completion behavior is acceptable.

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…