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:

daisyUI 5 is here: What’s new and what to expect

Explore daisyUI 5’s new features, performance upgrades, and theming engine built for Tailwind CSS 4 developers.

Ikeh Akinyemi
Aug 25, 2025 â‹… 8 min read
Why Kimi K2 is a frontend game-changer

Agentic AI for 5x less: Why Kimi K2 is a frontend game-changer

Kimi K2 doesn’t just tell you what to write or how to solve a problem; it writes the code, executes the tasks, and gets stuff done.

Chizaram Ken
Aug 22, 2025 â‹… 8 min read
Gemini CLI vs Codex CLI: A Comparative Analysis

Does Gemini CLI fall short? Here’s how Codex compares

Compare Codex CLI vs Gemini CLI for real-world coding tasks. See strengths, weaknesses, and which AI CLI fits your developer workflow best.

Emmanuel John
Aug 20, 2025 â‹… 8 min read
Is Next.js Still Developer-Friendly?

Is Next.js still developer-friendly?

The question isn’t whether Next.js is good or bad; it’s whether the productivity gains are worth the complexity tax.

Chizaram Ken
Aug 20, 2025 â‹… 5 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