Conduitry

I'm doubting we want to support several-year-old versions of browsers that update themselves by default, either.

We could perhaps ease people into this a bit, by issuing warnings rather than immediately breaking. It should be pretty straightforward to check at build time whether a given `_layout`...

`$page` _is_ already exposed. [These stores](https://sapper.svelte.dev/docs#Stores) can be used in every component, including layouts,

The issue here is that Svelte can't tell at compile time which elements might be custom elements, and which might be regular elements. Allowing `bind:value` on custom elements is essentially...

Thinking back on this, it might be fairly safe to distinguish custom elements depending on whether their name contains a hyphen. So theoretically that takes care of the question of...

My gut instinct is that, until we have more documentation of ancillary tooling on svelte.dev, that this isn't the sort of thing that should live here. It's not part of...

As instructed in the issue template: > Reproductions must be [short, self-contained and correct](http://sscce.org/) and must not contain files or code that aren't relevant to the issue — please do...

The `{#if}` block is just resulting in `(/*name*/ ctx[0] = "world")` - presumably it should also generate an `$$invalidate` call like other expressions in the template do.

This dates back a long time ago (I think Svelte 1?) where people would generally use HTML syntax highlighting when editing Svelte components, so we encouraged people to use `foo="{bar}"`...

This should be fixed now in 3.56.0 - https://svelte.dev/repl/3626169f4fe44351b6ed954afa4bf57a?version=3.56.0