Florian Spier

In a NX workspace after running `nx migrate latest` there is this message after `npm i` "Angular CLI could not be decorated to enable computation caching. Please ensure @nx/workspace is installed." I wonder if it is an issue since the NX commands (serve, lint) are working...

@Jean__Meche @if @Switch Good to know! Thank you!

@spierala @if @Switch Since v21.0, that migration is automatic and not opt-in anymore. The ngif/ngFor directives will be removed in the future.

Does upgrading to Angular 21 enforce the new control-flow syntax (`@if`, `@switch` etc)? (I am using `ng update @angular/core@21 @angular/cli@21`) Can I not opt-out anymore as in previous updates? #angular

@VojtechMasek @if @Switch I just tried `ng update` again. The app was auto-migrated to the new control-flow. There is no way to opt out. Maybe something changed with ng 21.2 ?

@spierala @if @Switch Updating Angular won't auto-migrate the control flow. There is separate (optional) migration for that. Also the structural directive based control flow will remain available. Ant in theory even it it was ever to be removed, you can still copy out these directives to your project

I just registered for NG-BE 2025 ti.to/ng-be/ng-be-20…

I think so! 🥳 ti.to/ng-be/ng-be-20…

Hey @ngbeconf, are there any plans for a 2025 edition of NG-BE? 🤞

NG-BE Conf tickets are available! 🎉 ti.to/ng-be/ng-be-20…

@Armandotrue App component never destroys. So no need to unsubscribe. When the browser window closes then the browser should clean up everything.

Serious questino to which I'm unsure if I have an answer Do we actually need to unsubscribe from Observables in the root component? 🧐

@Armandotrue In my experience ngOnInit was rarely really needed. One use case was to wait for @Input properties being ready. But if there is no reason to wait just declare the property directly. Less code, less Angular magic.

With #Angular signals, one of my most hated patterns will go away Just ditch the lifecycle methods!

@insanicae @Dutch_Guy @NxDevTools And the Angular dependency seems to be managed again by Nx... Now nx migrate also updates Angular as expected :) In the future I will be more careful with --interactive 😃

@Dutch_Guy @spierala @NxDevTools You can just nx migrate [at]angular/core[at]latest. Same with cli and it will all work 💪 runs migrations et all

Is it normal that Nx workspace does not migrate to a higher Angular version anymore? At least `nx migrate latest --interactive` used to ask if I want to upgrade Angular etc. Our project is using Nx 20.4.5 and Angular 18.2 The migrate command seems to update only Nx itself.

@insanicae @Dutch_Guy @NxDevTools This was now my command to upgrade to Angular 19 (which I previously skipped in interactive mode) nx migrate nx@20.5 --from=nx@20.2.0-beta.5 --exclude-applied-migrations

@spierala @Dutch_Guy @NxDevTools Ah, Well there we go 😅

@markgoho nx migrate latest creates a migrations.json... But running that migrations does not upgrade Angular.

@spierala then something is definitely off -- maybe try without the interactive flag? `nx migrate latest` should absolutely be producing a migrations.json file that has all of the changes to your workspace and angular to get you on the latest version of both

@Dutch_Guy CLI I tried several times the same command (nx migrate nx@20.4) without success.

@spierala Does it help if you run it multiple times? Also - are you using nx devtools or CLI?

@markgoho In my case there are no migrations to run...

@spierala nx migrate creates a list of migrations, then you have to run those migrations

@Dutch_Guy I just tried `nx migrate nx@20.4` and it does not update Angular. These are the only changes...

@spierala I noticed this to a few weeks ago. According to this link, 20.4 should support up to 19.1 so you would expect it to upgrade to that 🤷. nx.dev/technologies/a…

@eugeniyoz 🤔 What about ViewEncapsulation.None (which makes the component styling also global)? Why isn't it discouraged?

@spierala Because it is located in one component, but affects others, which should not happen by default. It is better to declare some global rule in the global style.css.

Why is Angular so strongly against ::ng-deep? If you read the docs, you almost do not dare to use it anymore. But I think in some rare cases it is fine to use it.