spikerj/spikersoft-issues
1
0
Fork 0
Code Issues 196 Pull Requests Actions Packages Projects Releases Wiki Activity

chore(deps): @fortawesome/angular-fontawesome 4 → 5 (major) #233

New Issue
Closed
opened 2026-06-17 02:57:47 +00:00 by spikerj · 1 comment
spikerj commented 2026-06-17 02:57:47 +00:00
Owner
Copy Link
Copy Source

Goal

Upgrade @fortawesome/angular-fontawesome from 4.0.0 to 5.0.0.

Why its own ticket

The angular-fontawesome major typically bumps its Angular peer range and may change the icon library/registration API. Keeping it standalone lets us verify the Angular peer independently.

Risks to check

  • Confirm v5 supports our current Angular 21 (peer range). If v5 requires Angular 22, fold this into the Angular major epic (#219) instead.
  • @fortawesome/free-solid-svg-icons is already on 7.2.0 — verify icon-pack compatibility with angular-fontawesome 5.
  • Review v5 changelog for FaIconComponent / FaIconLibrary API changes.

Validation

  • pnpm install clean (no Angular peer conflict)
  • nx build spikersoft succeeds
  • Manual: spot-check icons render across the app
  • pnpm test-all green

Fixes land in spikersoft-angular.

## Goal Upgrade `@fortawesome/angular-fontawesome` from 4.0.0 to 5.0.0. ## Why its own ticket The angular-fontawesome major typically bumps its **Angular peer range** and may change the icon library/registration API. Keeping it standalone lets us verify the Angular peer independently. ## Risks to check - Confirm v5 supports our current **Angular 21** (peer range). If v5 requires Angular 22, fold this into the Angular major epic (#219) instead. - `@fortawesome/free-solid-svg-icons` is already on 7.2.0 — verify icon-pack compatibility with angular-fontawesome 5. - Review v5 changelog for `FaIconComponent` / `FaIconLibrary` API changes. ## Validation - `pnpm install` clean (no Angular peer conflict) - `nx build spikersoft` succeeds - Manual: spot-check icons render across the app - `pnpm test-all` green Fixes land in `spikersoft-angular`.
spikerj commented 2026-06-17 05:40:58 +00:00
Author
Owner
Copy Link
Copy Source

Verified @fortawesome/angular-fontawesome@5.0.0 declares peerDependencies: { "@angular/core": "^22.0.0" }. We're on Angular 21, so v5 cannot be installed without a peer conflict.

Per this ticket's own guard rail ("If v5 requires Angular 22, fold this into the Angular major epic #219 instead"), this is blocked by #219 and folded there. Closing as blocked — will be picked up as part of the Angular 22 upgrade.

The app's FontAwesome usage is minimal (a single component, classes.component.ts), so the actual migration should be trivial once the Angular peer is satisfied.

Verified `@fortawesome/angular-fontawesome@5.0.0` declares `peerDependencies: { "@angular/core": "^22.0.0" }`. We're on Angular 21, so v5 **cannot** be installed without a peer conflict. Per this ticket's own guard rail ("If v5 requires Angular 22, fold this into the Angular major epic #219 instead"), this is **blocked by #219** and folded there. Closing as blocked — will be picked up as part of the Angular 22 upgrade. The app's FontAwesome usage is minimal (a single component, `classes.component.ts`), so the actual migration should be trivial once the Angular peer is satisfied.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#233