Conduitry

For the breaking change, what I meant was that, if someone were calling the `render` function manually, there would now be a new value returned that they would be expected...

IIRC we at some point had at least semi-blessed using this as a workaround for people who wanted actual `` elements in their components. Does that change anything for you?

It looks like what I'm referring to is #10641 and it also sounds like we have a way of addressing this in Svelte 5, but it also looks like this...

There has been at least a little bit of internal conversation about something like this. I had floated it as an idea for a way to let `$effect` functions know...

Please provide a _complete_ minimal reproduction. This contains several references to external files.

I think I vaguely remember this coming up before. I think it was related to the order that attributes are attached to the element - i.e., if `src` were attached...

Please write issues in English only. Please also don't use issues for support requests. It sounds like the CORS preflight request is getting back a redirect, but you haven't provided...

We should either update the "Various error and warning codes have been renamed slightly." note in the docs to say that _all_ error and warning codes have been changed from...

Changes that only occur in runes mode are not the sort of changes we're concerned with here. Breaking changes are instances where a user upgrades from Svelte 4 to Svelte...

Again, no, not for the purposes of documenting what the breaking changes are for people who try to use their components as-is when upgrading from Svelte 4 to Svelte 5.