yo VS nx

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?

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.

First let's install yeoman, a scaffolding tool for webapps, and yeoman's generator plugin for VSCode.

Nx 15.6: Release Notes

👩‍💻 Nx GitHub

We think that Nx is uniquely positioned to be an essential tool in this current generation of JS stacks.

The Nx ecosystem is excellent because, on the one hand, it allows different teams to work under the same monorepo and build robust enterprise solutions. On the other hand, the basic Nx functionality is relatively easy. That's why Nx-based solutions turned out more popular last time. Consequently, increasing monorepos include technologies such as React, Angular, NestJS, and even Golang. Moreover, these libraries and frameworks are not alone under the monorepos. They often use a lot of 3-d party libraries and custom modules. One of the most painful topics regarding software development, including Nx, is managing dependency updates. Especially dependencies with breaking changes that need to be resolved in order to get the application back into a working state. This article proposes one possible solution. It is not meant as a final solution and or source of truth. These are only initial thoughts about the topic.

My team has been using nx. There was a little bit of a learning curve, but it's working out pretty nicely. Code is split into apps and libraries, and nx takes care of setting up the import paths for the libraries. You can even tag some as frontend- or backend-only and it will warn you if you're importing a backend-only library in the frontend.

I'm talking about Nx. Nx comes with a set of plugins that come with code generation abilities and help abstract some of the lower-level tooling setups. And this can be really interesting for the use case we wanna tackle today.

Nx offers great out-of-the-box support and developer experience for Module Federation for Angular and React. You can learn more about it from the resources below:

To import ES Module libraries, your library should also be ES Module. See @nrwl/node application not transpiling to esm · Issue #10296 · nrwl/nx for more information.

nx.dev or https://preconstruct.tools/ or turbo.build if you have a monorepo

Maintaining TypeScript/JavaScript evolution is easy frankly, thanks to Nx which provides helpful migrations to various config settings to alleviate a lot of manual maintenance. TypeScript makes for easy and powerful refactoring so it's quite a joy in this department.