-
-
Notifications
You must be signed in to change notification settings - Fork 208
chore(deps): update nx to v21.2.0 & angular to v20.0.3 #1875
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
View your CI Pipeline Execution ↗ for commit 7804f72
☁️ Nx Cloud last updated this comment at |
hey @gestj thank u so much for this huge contribution <3 ! I was working on that already for a while, but didn't find time to finalize it, the current state is here #1876 I see that you put a lot of effort into this one, so I want to merge your PR over mine. Can u solve the remaining comments? I'm going to merge your PR then when pipeline succeeds and do the additional changes in a new PR. |
the demo build is failing https://cloud.nx.app/runs/PxeR6ftRdG/task/demos%3Abuild%3Aproduction it's just a couple of minor changes. Do you want to take care of them? |
Also related: #1877 |
Heyho, thanks for taking over. I am currently off due to private issues, I didn't see your comments until now. Still not ready. I had a look on failing test (https://cloud.nx.app/runs/RKoxUB9h0R/task/template%3Atest). I think I found a valid fix for that one. |
This one seems to be resolved as well by changes from @eneajaho. Command runs successfully localy. |
…?, ?) https://cloud.nx.app/runs/RKoxUB9h0R/task/template%3Atest From all I know, it isn't needed to provide core Angular "providers" unless you want to explicitly overwrite it with some custom implementation.
Some other thing. When I run locally
I get a big chunk of changes. Is the project in some corrupt formatted state? (I won't push this change) |
FINALLY, the main pipeline is green. |
We also can't update to Angular 20 because of
rx-angular
staying behind.So, I started this branch & rather big update. The 20 update is painful. Its big with many changes for big / complex projects. We also suffer in our project.
I hoped I could make it work for
rx-angular
which is less complex than ours.But sadly, it isn't that easy in this project as well.
I of course struggle with the tiny details since I am not used to behind-the-scenes coding tightly coupled to deep nasty details of Angular framework.
This failing test in stopped my approach for now.
libs/template/unpatch/src/lib/tests/unpatch.directive.spec.ts
BUT; Maybe you can make use of it if you consider an Angular 20 update.
PLEASE; Take over. I won't be able to successfully make this ready for merge.
Maybe, what did I do?
The migrations of NX & Angular will change a LOT of files. E.g. the template changes where
ngIf
,ngFor
,ngSwitch
get replaced by their control flow counter parts. Others are config changes by NX migrations.After that:
@angular-eslint/prefer-inject
where needed (and in one place I fixed the issue since it was only one spec file).test-setup.ts
files (the wayjest-preset-angular
works changed with 14.6.0)toObservableMicrotask
since API change due to fix(core): removeforceRoot
flag for effects angular/angular#60535 (part of Angular 20)zone-config.spec.ts
you patchZone
in window; This broke. I disabled (commented) the relatedbeforeAll
&afterAll
. I had this idea after I saw how tests are written. I asked myself why the hell is this needed in first place, I bet it works without it. And yes, the tests run with out it. But, I can't judge it since I don't know the code by heart....