ReferenceError when running SSR version of a component

[divdavem]

Describe the bug

The following component:

<script lang="ts">
	import MyComponent from './MyComponent.svelte';
</script>

<MyComponent>
<slot name="otherComponentSlot" slot="myComponentSlot" let:props {...props}></slot>
</MyComponent>

is transformed into the following JS when using SSR:

/* OtherComponent.svelte generated by Svelte v4.2.0 */
import { create_ssr_component, validate_component } from "svelte/internal";

import MyComponent from './MyComponent.svelte';

const OtherComponent = create_ssr_component(($$result, $$props, $$bindings, slots) => {
	return `${validate_component(MyComponent, "MyComponent").$$render($$result, {}, {}, {
		myComponentSlot: () => {
			return `${slots.otherComponentSlot
			? slots.otherComponentSlot({ slot: "myComponentSlot", ...props })
			: ``}`;
		}
	})}`;
});

export default OtherComponent;

Note that the prop variable used in myComponentSlot is not defined anywhere, which results in a ReferenceError at runtime.
When using normal (browser not SSR) compilation, the component works fine as expected.

Reproduction

https://svelte.dev/repl/e9dad6e75c8041c1be79c2e07a82fc51?version=4.2.0

Logs

No response

System Info

Svelte v4.2.0

Severity

annoyance

[divdavem]

Note that, as a workaround, it is possible to use instead the slot inside a svelte:fragment:

<script lang="ts">
	import MyComponent from './MyComponent.svelte';
</script>

<MyComponent>
<svelte:fragment slot="myComponentSlot" let:props><slot name="otherComponentSlot" {...props}></slot></svelte:fragment>
</MyComponent>

[dummdidumm]

Fixed in Svelte 5