2021-05-10
1224
#angular
Emmanuel John
47591
May 10, 2021 ⋅ 4 min read

Angular modules: Best practices for structuring your app

Emmanuel John I'm a full-stack software developer, mentor, and writer. I am an open source enthusiast. In my spare time, I enjoy watching sci-fi movies and cheering for Arsenal FC.

Recent posts:

DesignCoder and the future of AI-generated UI

From sketches to code in minutes, DesignCoder shows how AI-generated, hierarchy-aware UIs could change the way developers prototype and ship apps.

Rosario De Chiara
Oct 7, 2025 ⋅ 5 min read

Would You Use If() functions in CSS?

It’s 2025, and CSS finally thinks logically. The if() function brings real conditional styling — no hacks, no JS workarounds. Here’s how to use it right.

Ikeh Akinyemi
Oct 7, 2025 ⋅ 16 min read
Typescript or Zod for Validation?

TypeScript vs Zod: Clearing up validation confusion

Learn when to use TypeScript, Zod, or both for data validation. Avoid redundant checks and build safer, type-sound applications.

Alexander Godwin
Oct 6, 2025 ⋅ 3 min read
Wasm 3 Before GTA 6 LogRocket Article

We got Wasm 3.0 before GTA 6: Meet the web’s new engine

Discover how WebAssembly 3.0’s garbage collector, exception handling, and Memory64 transform Wasm into a true mainstream web platform.

Ikeh Akinyemi
Oct 3, 2025 ⋅ 2 min read
View all posts

One Reply to "Angular modules: Best practices for structuring your app"

  1. Cannot agree with all of this.
    First of all, what is the difference in your definition of share and core modules?
    Preferable way is to create single core modules with all services provided in root and create some libs outside of app for better visualization of lazy load.
    All this feature staff is not important, it’s better to have all the code you in one place.

    Also I like the rule that you should import only from your own folder and inside, and never go up.

    PS auth via Twitter does not work, via goglogle.works but breaks on post. Are you sure you are logging everything??

Leave a Reply