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.

What if we created one module for each component?

That is what the SCAM means. It stands for .

As far as I know, this term was coined by in his article about .

I loved the concept so much that I created a simple schematic for that.

You can use it right away like this:

This will generate the following file structure:

In a response to this article, from the Angular Core Team suggested to just move the NgModule to the .component.ts file and simply get rid of the .module.ts.

It totally makes sense for two reasons:

Well, same applies for directives & pipes. SDAM & SPAM?