Angular Spotify #1: Structure your Angular application with Nx workspace

In this first tutorial of Angular Spotify, let find out how to structure your Angular application with Nx workspace in Angular Spotify application. Also, we will start building the browse page so that you can start to explore more music on Spotify 🤣

Question
Meo Di Bui: We just migrated from multi repos to NX monorepo to take advantage of shared libs, UI, data model. What a game-changer! In the case of multi projects, what is the strategy for deployment for them?

Chau: Look into this article where you can utilize Github actions for deploying only the affected apps.

Should I Make a New Library?

Library Types

[tanuwo]

Thanks a đã chia sẻ. cách tiếp cận này khá mới chắc phải xem thêm các video nữa của a để hiểu hơn. Nhân tiện đây có phải là cách mà mấy thằng như ng-zorro hay prime-ng đang dùng k ạ

[hoangbao]

Thanks for the very detail and friendly tutorial, looking for more stream in future. from ybg with <3 :))

[WellingtonTorrejaisdaSilva]

Nice work! Could you do some zoom on browser text font size in next videos? Thanks!

[nguyenhoa]

Hi Mr. Trung,
I downloaded your project, read it in detail. The structure is really strong, adaptive, and scalable. Checked your videos about Angular Spotify also but there are some points I cannot get your idea.
> Why do we need a lot of boilerplate (eslint, tsconfig, ...) wrapped by src/lib folder? I know it comes from CLI but it should be flattened, is it?
> Is there another way to handle it by Nx?
Thank you so much! Great job!

[boyefrederic]

Hi all, Good content, Can you please show us the scripts to add tailwind to nx project

[moitp]

I would like to raise a concern about arguments used about 46 minutes in that video.

I still think that's quite over engineered there. SCAM can clearly be done without creating a new lib for each components. Yeah those components will all be in the same lib, but they will still be done following the SCAM principle in a module. You can also split your components into multiple libs following your concerns.
For the circular dependencies issues, that's also managed by following SCAM.

The only benefit that's can't be done without your solution is building every component separately. But does it really matter ? Appart if you are going with module federation to create micro services, I don't see any point to build everything separatly. You will gain some time during the build process (does it really matter ?), but at the cost of way more boilerplate and an approach less understandable for a new commer. And I am not even talking about the whole CI/CD to configure behind the scene to make everything works as intended.

Overall, your project is amazing tho, well done !