Nx vs Angular CLI - The Showdown

[@sakarsr]

Wonderful session on Nx with Angular, I already use it in my Angular projects and save lots of my time in creating Angular apps. Thank you for the time to make this video. Have a nice day and good health. Make a Nx with Fastify video.

[@nxdevtools]

Thanks! Here's a video about Fastify: kzbin.info/www/bejne/gnmviGOYaculaNk - Juri

[@spastata]

Thanks Juri! Really nice insights

[@CFXTBogard]

Note to use Peacock to change the color of VSCode. it would be useful to differenciate Nx project window agains Angular/cli project.

[@amosisaila8416]

Can you tell me what theme are you using for VS code and the icons theme? Thank you. Great video.

[@LarsRyeJeppesen]

What if we have to build docker images as part of the builds? (nodejs, the build has to happen inside docker due to the target architecture) Curious to figure that out

[@KiffinGish]

When using the example for customizing the webpack config as explained in the video, I get the following error: Data path "" must NOT have additional properties(webpackConfig). at name (/home/kiffin/qcarbon-next-frontend/node_modules/@angular-devkit/architect/src/architect.js:223:19) at processTicksAndRejections (node:internal/process/task_queues:96:5)

[@barperetz18]

What is your theme for the style? colors font etc

[@Matheus_1582]

Oi, eu queria saber se da pra criar um projeto FrontAnd...???

[@TiagoWankeMarques]

Great video, tnks for sharing so much info. Is there any official pronouncement from the Angular team about NX or any other similar tool? It looks to me that would be a good decision to let tools like NX to manage workspaces (which have a broader scope than just Angular) and remove this from the Angular’s team responsibilities so they can focus even more on Angular related issues.

[@zlatkorekic]

Thanks @Juri, any chance that nx console supports debugging of nx commands?

[@nxdevtools]

Not 100% sure what you mean with debugging. But if that's code-level debugging, you can already do that (say in VSCode), where you just go into the node_modules/@nx/... the package you want to debug and set a breakpoint - Juri

[@arozendojr]

Do you know why the NX test, with Angular, skips the app.config.ts and app.routes.ts files during the test coverage report?

[@codearabawy]

Can you please share with us what theme you're using in VS code? I really like it.

[@muhammadidrees6650]

I think he is using Night Owl. I could be wrong though :)

[@codearabawy]

@@muhammadidrees6650 Thank you very much, Muhammad!!! Yup, it's the correct theme I think. ;)

[@RajkumarPattnaik]

Great 👍

[@eelcolos0451]

How about ng/nx serve being cacheable? I recall (a now defunct) conversion with the angular cli? (decorate-angular-cli.js)

[@joylaurencesangalang5457]

Please fix the issue in next and emotion

[@juristr]

Do you have a GH issue for this? Or can you open one? 🙏 thanks a lot

[@moitp2]

I still need to understand the benefits off splitting into so many small libs adding extra boilerplate in the process and complexity for newcommers. Splitting is nice, but at at one point, I fill it becomes a gimick instead of a real need. Edit: I am talking specificaly on project that are creating a lib per feature, thing I have seen a lot recently in blog articles (and I am not talking about module federation).

[@KaliaH]

I have the same blockers. I’m a bit overwhelmed, but very curious.

[@yumeshinoroi2731]

AFAIK, it's because of the building time. The more you split features up to libraries, the lesser dependencies per library.

[@KiffinGish]

The command `npx nx g @nx/angular:lib products --directory features --standalone` does not create a products directory under features directory. I had to use `npx nx g @nx/angular:lib products --directory features/products --standalone` to get it working like in the video. The same applies when creating the orders feature. Also, the `tsconfig.base.json` file `paths` value is not the same: "paths": { "orders": ["features/orders/src/index.ts"], "products": ["features/products/src/index.ts"] } Thus NOT with the `@myngapp` prefix.

[@juristr]

Hey! Yeah, the TSConfig paths got fixed. We had removed that in one of the Nx versions but brought it back because it just made more sense to have that in the alias. For the folder not being created: yeah this is kinda intentional. Before we would "derive" the path based on the library name etc. Now however we give that decision to the user, s.t. you can directly provide it via the --directory flag