Matthew Conlen

(and thanks for your patience as I'm a little slow responding to issues, dealing with many things on my plate the last few weeks)

It would be good to get this in with v5, since it will be a breaking change.

Thanks @eyeseast. Agreed that the first thing to do is clean up the AST documentation and potentially get #358 in as part of that. @manjhawar96 and I are meeting this...

I'll write out a step-by-step algorithm for the logic that the current runtime implements. Is there any suggested reading where I could learn more about how Svelte (and preprocess) work...

Yes, I think that's right @eyeseast - I could imagine extracting the runtime to vanilla JS, although we'd have to think through exactly what the API would need to look...

Hey @jarmitage - this never really took off. I think the best short term solution would be to create a version that allows users to write svelte components while keeping...

Sounds good @jarmitage, thanks! One thing that would really help since I'm not yet familiar with all of the ins and outs of svelte is what needs to be done...

Okay thanks @jarmitage! Maybe @eyeseast would also know something about this.

Hey @eyeseast no worries thanks for the heads up. I'm reaching out to the svelte folks now to learn a little bit more about the architecture and will post here...

Okay - small update. I'm able to get svelte components compiling inside of idyll by using the [sveltify](https://github.com/TehShrike/sveltify) plugin found here to transform them to standard JS at build time....