TB Angular upgrade 19#7132
Open
cdavalos7 wants to merge 2 commits into
Open
Conversation
71d79d8 to
a034be6
Compare
arcra
approved these changes
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation for features / changes
Migrate Angular from 18 to 19 following the Angular update guide. As a side change, Node.js is also upgraded from 18 to 22.23.1 LTS to prepare for the next major version step.
Technical description of changes
Angular 19 changes the default value of the standalone flag to true, which means any component, directive, or pipe that omits it is now treated as standalone. This repo is fully NgModule-based, so all 206 declarations already had standalone: false set explicitly from a prior migration step. No changes were needed and the build compiled clean.
Detailed steps to verify changes work correctly (as executed by you)