Replies: 3 comments 1 reply
-
nx 13.0.0 is not compatible with angular 13 yet. It's a lot of work to ensure that nx is fully compatible with angular.
are all tools that are not supported by angular, but by nx. in angular 13 they changed to a ESM only output. also there might be things that need to be migrated. so when a new version of angular comes along it usually takes a couple of weeks before the ecosystem and the people at nrwl have the time to catch up. my wild guess is that we are close, since jest-preset-angular is at 11 rc4 and it has been a couple of weeks. when they release which will probably be nx 13.2 just running |
Beta Was this translation helpful? Give feedback.
-
Is NX now officially compatible with Angular 13? The question on google returns this as first answer: |
Beta Was this translation helpful? Give feedback.
-
I'm trying to figure out what are the intended steps to migrate
nx 12
workspace withAngular 12
project to the latest versions (which are 13 for both).What I tried:
Firstly, as a newcomer, I tried
ng update
and was faced with a suggestion to runnx migrate latest
(this one is neat).After I run
nx migrate latest
I realized that it only updates nrwl-related packages (still neat but that is half of the work).Then, since nx states that
nx migrate
is a better version ofng update
I tried to adapt what I usually tend to do while updating angular (ng update @angular/cli @angular/core
) but via nx, so:nx migrate @angular/cli @angular/core
. But it's turned out that only the first listed package was updated which is definitely not what I want.After that I started running a separate
nx migrate <PackageName>
for each of the packages from mypackage.json
but then gave up since to me it feels like I'm missing something and there should be a simpler way to update Angular and its deps.
Beta Was this translation helpful? Give feedback.
All reactions