yo VS nx

Maybe recheck the name ? https://www.npmjs.com/package/yo https://yeoman.io/

FYI, the name of the tool conflicts with the well-known project-scaffolding generation tool yeoman (which also uses yo as the program name)

Yeoman

I am familiar with Yeoman but the project appears dead. There are no replies to recent comments and the last release was a year ago. I would prefer to not use a dead/dying project as the basis for a new work. Does anyone have any suggestions?

The next best option would be yeoman - https://yeoman.io/

you're probably thinking of yeoman https://github.com/yeoman/yo

We'll need to install the Yeoman scaffolding CLI tools as well as the generator.

Have you tried yo? Haven't tried it much so can't say for sure but it's a pretty common recommendation for project generators.

I used Yeoman to generate the scaffolding. Make a project folder and run:

Nx Documentation: Monorepos Made Easy

Take Nx as an example. Head over to their Issues tab, pick a bug, and try to reproduce it. Then read through the code, understand the business logic, and make a fix. If you manage to create a successful pull request, congratulations—you just did the same thing professional developers do daily.

Nx Documentation: https://nx.dev/ - Official documentation for the Nx build system.

🏗️ The Umi's plugin system and API is quite interesting. You can do a lot with that. The approach is quite common for dev tools and in this case resembles both Vite and Nx with their extensibility and community orientation. There's a huge ecosystem of plugins of all sorts, and you can always complement them with your own (which is quite important for sophisticated enterprise development). I'd assume you could build pretty decent metaframework mechanisms with this flexible approach. At least, as I mentioned already, you have a bunch of thoughtful building blocks for that.

Nx is our choice for managing the project's monorepo structure. It provides powerful tools for scaling our development process, ensuring code reusability, and maintaining consistency across different parts of the application. With Nx, we can efficiently manage multiple projects within the EczEase ecosystem, from the main web application to potential mobile apps and backend services.

Hello! I used to like NX a lot. It was a monorepo for all my projects—different brands and clients in one place. It worked well, but it didn’t suit me. Most of my projects are single Angular apps. So, I stopped using one big NX repo and made separate projects instead. Here’s why I prefer it.

The project is using Nx workspace + PNPM for package management

Then there’s the tooling. Micro-frontends aren’t as plug-and-play as a monolith yet. You’ll likely need custom build pipelines, deployment scripts, and a solid CI/CD setup. Tools like Nx can help here—its monorepo approach is a lifesaver for managing multiple micro-frontends in one cohesive workspace. Their micro-frontend guide is worth a peek if you’re curious.

Nx (sponsored the Lightning Talks)