We recently released a huge update on our CI offering (Nx Cloud), including Nx Agents (a one liner to distribute tasks across multiple machines), fine-grained e2e test distribution, flakiness detection and more. We currently run a promo that gives you 2 months free trial on the Pro plan to properly test drive Nx Agents on your project: nx.app/campaigns/pro
I still didn't understand the significance of it. For eg: I have a .NET 8 backend Web API and Angular 17 frontend. So Nx helps me put them together in the same Git repo? I'm already doing that. What values does it bring? Can you please explain? Thanks!
Imagine your backend produces an openapi.yaml spec, and your front-end consumes that spec and generates a client. nx can be used to only regenerate the client in your front-end if the backend produces a different openapi.yaml spec. Or... at least that's my understanding.
No. Nx helps to modularize typescript and JavaScript projects in the same repo. But for the c# and angular u can use openapi spec like guy above wrote. The benefit is that u can have different linting and compilation strictness for that, so u don’t need to loose rules for the rest of the code. Nx will also cache the builds so they will build locally faster. If u have package per feature or module on ur website u can decide do share it with another team easily even if they have their own repo. The bundle size is also more manageable because of a possibility to split the dependencies. That also helps with more managable deps definitions, bc I already saw package json with tens of random deps. I’m in the middle of migrating old AngularJS app. I can’t rewrite it at once so I create small features and expose them as web components. Then I can import and use them natively in the html templates without worrying about react js angularjs integration. Also once I have autogenerated apis I can publish them in the company repository so the other teams could use it for example. I could even have totally different teams working on many products in one repository sharing some design system components. They could even be in different frameworks as the web components are in the mainstream now. It really depends on the situation.
Forgot to mention that u could have backend and front integrated using nx but that would require having it in TS or JS. Which for 99.999% of business CRUDs would be enough. In that case nx could easily take care of the above I already wrote
I’m not an NX expert tho. I literally started to migrate my blob on Friday when one guy in the company suggested it. I already see a lot of benefits. Integrating it into existing app is trivial, but extraction to libs is medium lvl difficulty. Depending how tightly coupled is ur code. For the next projects some monorepo tech will be my golden rule.
Sorry, I could not understand the benefits of this product. Maybe it would be better to show the top 5 common use cases that you can't do otherwise in a simple way.
So far its strange to get into nx, the documentation is missing a quick reference how start and build an application, so far im only getting errors " Inner Error: ReferenceError: structuredClone is not defined"
"This is NOT a component library. It's a collection of re-usable components that you can copy and paste into your apps." Never used shadcn, according to their docs you just need to install the library and copy and paste into your project the component you want. According to your project needs it would go into the main project folder or into the shared-ui one if needed
@@86tiagonuneswe're looking into this! Seems like nx generators might be a great way of managing some of those manual steps required for some of the components like adding tailwind config (and the initial setup too!)
I'm probably stupid but I don't really see a use case for this? It seems like taking extra steps just for the sake of taking extra steps... but I guess you can bill more hours to your clients, lol.
We recently released a huge update on our CI offering (Nx Cloud), including Nx Agents (a one liner to distribute tasks across multiple machines), fine-grained e2e test distribution, flakiness detection and more.
We currently run a promo that gives you 2 months free trial on the Pro plan to properly test drive Nx Agents on your project:
nx.app/campaigns/pro
I still didn't understand the significance of it.
For eg: I have a .NET 8 backend Web API and Angular 17 frontend. So Nx helps me put them together in the same Git repo? I'm already doing that. What values does it bring? Can you please explain? Thanks!
Imagine your backend produces an openapi.yaml spec, and your front-end consumes that spec and generates a client.
nx can be used to only regenerate the client in your front-end if the backend produces a different openapi.yaml spec.
Or... at least that's my understanding.
No. Nx helps to modularize typescript and JavaScript projects in the same repo. But for the c# and angular u can use openapi spec like guy above wrote. The benefit is that u can have different linting and compilation strictness for that, so u don’t need to loose rules for the rest of the code. Nx will also cache the builds so they will build locally faster. If u have package per feature or module on ur website u can decide do share it with another team easily even if they have their own repo. The bundle size is also more manageable because of a possibility to split the dependencies. That also helps with more managable deps definitions, bc I already saw package json with tens of random deps.
I’m in the middle of migrating old AngularJS app. I can’t rewrite it at once so I create small features and expose them as web components. Then I can import and use them natively in the html templates without worrying about react js angularjs integration. Also once I have autogenerated apis I can publish them in the company repository so the other teams could use it for example.
I could even have totally different teams working on many products in one repository sharing some design system components. They could even be in different frameworks as the web components are in the mainstream now.
It really depends on the situation.
Forgot to mention that u could have backend and front integrated using nx but that would require having it in TS or JS. Which for 99.999% of business CRUDs would be enough. In that case nx could easily take care of the above I already wrote
I’m not an NX expert tho. I literally started to migrate my blob on Friday when one guy in the company suggested it. I already see a lot of benefits.
Integrating it into existing app is trivial, but extraction to libs is medium lvl difficulty. Depending how tightly coupled is ur code.
For the next projects some monorepo tech will be my golden rule.
Sorry, I could not understand the benefits of this product. Maybe it would be better to show the top 5 common use cases that you can't do otherwise in a simple way.
Exactly , I’m just listening and can’t understand what problem it solves
Great tutorial! Very useful for those new to Nx and unsure about it.
Juri is the best!!
So far its strange to get into nx, the documentation is missing a quick reference how start and build an application, so far im only getting errors " Inner Error: ReferenceError: structuredClone is not defined"
what the name of the vscode theme you use in the video ?
Night Owl - Juri
Nx is stable and awesome, i learned about monorepo tools by Vercel Turbo but it's super unstable and bad experience.
can anyone please tell me why project.json is created when i create a library using Nx console ? Thanks 😊
Great video for a quick overview thx!
Juri is the best!!
What about multiple languages in the same repo?
Can I have a node/react frontend and Deno backend in one Nx monorepo?
Yup! You can even share certain TS libraries between the two. Checkout github.com/nrwl/deno-livestream as an example here :)
Stumbled over this while getting into Nx but I have a different question at the moment ... what color theme and font is that? 🙂
The important questions 😅. This is Night Owl & Jetbrains Mono as the font iirc (need to check later at the computer)
We need a tutorial on how to use shadcn/ui in a nx monorepo.. how to set it up and how to configure shadcn/ui cli in nx.
good idea. I don’t think there should be anything special you need to do. I’ll look into that 😀 - Juri
"This is NOT a component library. It's a collection of re-usable components that you can copy and paste into your apps."
Never used shadcn, according to their docs you just need to install the library and copy and paste into your project the component you want. According to your project needs it would go into the main project folder or into the shared-ui one if needed
@@86tiagonuneswe're looking into this! Seems like nx generators might be a great way of managing some of those manual steps required for some of the components like adding tailwind config (and the initial setup too!)
I wish more tech RUclipsrs (like fireship) used analogies and examples first before bombarding with technicalities. Nevertheless, thanks.
Wow, you use vim-mode 😎 Cool 💪
haha, yeah I do. It is an extension for VSCode. I like it
I'm probably stupid but I don't really see a use case for this? It seems like taking extra steps just for the sake of taking extra steps... but I guess you can bill more hours to your clients, lol.
0:37 monirul islam bhuiyan ❤
Nx हिन्दी me
.)
😢
getting Nx Failed to create a workspace when running npx create-nx-workspace.