Every time I am about to add a component to an Angular application, I feel like there is a bunch of people arguing in my head.

There’s a to generate Single Component Angular Modules.

A while ago, I caught this Pull Request from which shows that the Angular team might make NgModules optional in the future.

It inspired me to experiment a new .

The current problem with this approach is that in addition to involving a new syntax, we will have to wait for optional modules support.

By the way, here’s ’s reaction about my previous post and optional modules:

In the meantime, we have to consider another way to solve this situation.

One of the main challenges with NgModule is refactoring.

Given the following cute and tiny little module:

It is already a challenge to move to another module.

For instance, it is hard to tell if & should be kept, moved, or duplicated to the new module.