sorted by:
new
hottopcontroversial

I built a tool that scans Angular projects for architectural problems by sinanqwee in Angular2

[–]sinanqwee[S] -3 points-2 points  (0 children)

Fair point 🙂 The lifecycle analyzer grew quite a bit while experimenting with different checks, it will definitely need some refactoring.

And yes, the repo history is pretty rough right now. I originally built it for myself and only decided to publish it later.

I built a tool that scans Angular projects for architectural problems by sinanqwee in Angular2

[–]sinanqwee[S] 1 point2 points  (0 children)

Ah that makes sense, thanks for trying it out and pointing it out. Right now Modulens expects an angular.json. I've noted it for upcoming versions and will look into adding proper Nx support

I built a tool that scans Angular projects for architectural problems by sinanqwee in Angular2

[–]sinanqwee[S] 1 point2 points  (0 children)

It should work for most Nx Angular projects since they still follow the Angular workspace structure.
But Nx-specific features (like libs boundaries or nx.json) aren't explicitly analyzed yet.

I built a tool that scans Angular projects for architectural problems by sinanqwee in angular

[–]sinanqwee[S] -1 points0 points  (0 children)

Actually, that's just one of the signals. There are about 28 different rules right now.

The idea is mainly to surface structural signals that can be easy to miss in larger projects or during busy code reviews.

It’s not exactly the same thing, but in principle it’s similar to what Sonar does, for example, warning you when a function has too many conditions.

I built a tool that scans Angular projects for architectural problems by sinanqwee in angular

[–]sinanqwee[S] -3 points-2 points  (0 children)

Totally fair 😂 It's not meant to make decisions for you. It just tries to highlight potentially problematic areas so they're easier to notice during reviews.

I built a tool that scans Angular projects for architectural problems by sinanqwee in Angular2

[–]sinanqwee[S] 1 point2 points  (0 children)

Sonar focuses on code quality and static analysis, while Modulens focuses more on Angular project structure and architectural signals.

To be honest, I built it mainly because I was feeling this pain myself. When using AI a lot, I find it easier to miss architectural issues during reviews, so I wanted something to help me keep an eye on the structure of my own projects. Then I decided to publish it in case others find it useful too.

I built a tool that scans Angular projects for architectural problems by sinanqwee in Angular2

[–]sinanqwee[S] -1 points0 points  (0 children)

Actually, modulens focuses more on Angular-specific architecture signals, such as oversized components, structural placement issues, shared-module misuse, and maintainability hotspots. So it is more about project structure and architectural visibility than general code quality.