Aiden Bai

> > Not yet. Have been somewhat busy, currently still investigating > > if anything i can do, pls let me know. Currently, I'm trying to figure out why Million...

Hey @AlexJeffcott, thanks for your interest in Million! Suspense/Fiber (as well as the limitations described) are on the roadmap. I'm currently working on pressure testing Million against libraries by trying...

Hey Kent, functional components don't have boundaries at the moment. This is a good feature suggestion, thanks for the feedback!

@kentcdodds @QuiiBz just shipped this in v1.12.3! and an awesome writeup by them here: https://twitter.com/tomlienard/status/1557448841196146688

I'd love to take on this issue, unless anything has popped up recently that has changed your mind @Holben888

Hi@DaniAkash, Next.js is currently not compatible with Million.js. We are planning to work on a next plugin to allow for this in the future.

Sure! We're currently working towards some compatability with routers currently in order to support Next.js router in #203. Next steps are hydration, prerendering, etc. Feel free to join our Discord...

Hi @ccorcos, thanks for your interest in Million and happy to answer your questions. > I'm seeing the diff code here, but that looks like its happening at runtime? 🤷‍♂️...

> So regarding the compiler, what exactly is the optimization here? It looks like it's unwrapping components into one large single component? Is that what's going on? I'm also curious...

Referencing this issue to the main repo! https://github.com/aidenybai/million/issues/260