Angular

266 readers

2 users here now

A community for discussion about angular

Wormhole

!godot@programming.dev

Logo base by Angular under CC BY 4.0 with modifications to add a gradient and drop shadow

founded 1 year ago

MODERATORS

Ategon@programming.dev

fabian@programming.dev

Micro frontends (lemmy.world)

submitted 1 year ago by TheGiantKorean@lemmy.world to c/angular@programming.dev

7 comments fedilink hide all child comments

Does anyone have experience with breaking apart a large Angular frontend into micro frontends? Any advice you can offer or resources you can point me to would be greatly appreciated. Ideally I'd like to be able to mix Angular versions and different technologies (e.g. React) in the future as well, assuming that's possible.

you are viewing a single comment's thread
view the rest of the comments

[–] emma@programming.dev 2 points 1 year ago (1 children)

What you are describing loosely sounds like the islands archetecture that Astro uses (however I have no idea if it lets you mix angular versions; that sounds cursed)

Astro is a meta-framework like Next.js. Unlike Next.js, however, you could do exactly what you are describing. You can use both React and Angular (and even Vue and Svelte) components all in the same meta-framework.

Additionally, you opt-in to all and any client-side interactivity. If you have components that don't do anything after the page loads, you don't have to client side render them.

With that all being said, this might be totally unhelpful to you, but this is just what reading your post made me think of. I wish you luck in your breaking down of a large angular frontend.

[–] TheGiantKorean@lemmy.world 1 points 1 year ago

Thank you! I will definitely look into Astro. The concept of islands sounds very interesting and kind of what I had envisioned initially before we were looking at build time integration.