Ryan Carniato

Yeah. I built this so that while it can handle moves that when the element has been disconnected I free up reactivity (basically dispose) and when connected I create again....

Is there a place where you hit this as a bug?

Ok the reason I asked is mostly it is a hot path and if it isn't neccessary Id skip. Plus we don't transpile and there are envs that don't support...

Not currently. The compiler plugin is pretty complex and still actively being worked on. There has been some looking into SWC and Bun, but today that requires building the compiler...

Hmm... trying to figure out if this is an annoying message or not. Haven't vetted enough projects to know if this is common place. What drew your attention to this?

I've been slow on this one (and it has come up before) mostly in that we need to apply the support in at least 4 places including client and server...

SSR and even hydratable client both use different transforms than the standard client and leverage additional runtime behaviors. Hydration for a framework like Solid has been pretty tricky to figure...

I think the other thing to solve is spreads if we want components to be able to forward these. This proposed solution came up during 1.0 rc time period but...

This was to fix getter/setters etc in custom elements. I couldn't figure out why it was always working properly in Lit and not Solid. This effectively lets us upgrade before...

Yeah literals have a different branch of code in the compiler. I likely missed that one.