Michael Geers

This is indeed a tricky topic. Features inside one vertical are tested by the team itself. This is where we write most of our tests. To make sure all pieces...

> There is no one size fits all solution and assembling all of these parts can happen on a spectrum of choices. Thats definitely the case. We've used different approaches....

Polyfills are in deed a little bit tricky. We are using two different approaches here. The first one is **conditional execution**. So every team ships the polyfills they need, but...

As always it depends on how you implement it. I'll write more in depth about "performance" in the future, but in essance it boils down to "keeping it simple, only...

Hi @ido-ran, thanks for your work and sorry for my late response. I don't have experience with Netlify, but being able to run all examples on the web would be...

Have you seen the product page example in the Repo? Up until now I only address integration on one page and data fetching/skeleton there. I’m planning to add more examples...

Yes, if you want client side page transitions you would have to establish a shared [top-level router](https://speakerdeck.com/naltatis/micro-frontends-building-a-modern-webapp-with-multiple-teams?slide=38). This could also be done in a way that works server-side. [single-spa](https://github.com/CanopyTax/single-spa) does...

Hi @amazzoccone, Yes I would give every fragment/component it’s own data fetching and state management and it’s totally fine if a team decides to use GraphQL internally. It would also...

Thanks for the issue. I've noticed similar effects from time to time - even with the previous design. I'll try to reliably recreate this issue to come up with a...

👆 I've introduces a dedicated offline indicator. It will help debug this issue but is also a general improvement since evcc usually only works in your lokal network.