rixo

Sorry for being late to the party, this had escaped my vigilance. As I understand the RFC, this is mostly increasing stability by removing buggy edge cases, and adding more...

Sorry for taking so long to come back at this... So, you're right, your REPL is exactly what I had in mind, "content for the default content". I misread the...

The problem with using a custom syntax like `{#slot}` is that we lose the parallel that already exists with native (custom elements) ``, and where `slot="name"`, like Svelte currently, also...

I would love this too! My use case is documenting a tool by writing some sort of self-describing document. Here's some example of what I currently do (the new syntax...

It was used to add the --single flag to sirve, in the custom server plugin that has changed during last merge. You need that for non hashed-based client side routing....

Yes that's what I'm referring to. Apparently unsolved upstream... I guess we can just drop the const for now and follow suit if they take any decision :shrug:

I have no real idea how sourcemaps works in Nollup (or generally otherwise...), but you can probably fix this by adding a middleware to serve contents from `/node_modules/` if that's...

I was surely tired previously, it's obviously not a sourcemap problem. It's a more of a dev server problem. No it wouldn't impact performance in any meaningful way... Like we're...

Yes, we do. Default behavior has been changed from preserving the value of all variables, which was understandably confusing people, to not preserving the state of any variable except those...

I think Typescript is misguided... Whatever, it's just my own limited personal opinion, if it's supported by the official template it should work here too. Can't tell if it will...