Site REPL started "hanging" as I tried to produce an example for a different bug

[PixievoltNo1]

Describe the bug
As I was trying to put together a demonstration for a different bug, the REPL seems to have entered a state where not only can it not compile the demonstration, it also cannot react to any changes in the code, and cannot save any new versions (attempting to save gets a window.alert box saying "r is null"). I can load the version I somehow managed to save already, but this just puts the REPL back in the same state.

Logs
The "Result" pane has a message stuck on "bundling ./App.svelte".

The browser's console says:

Console was cleared.
running Svelte compiler version 3.20.1
Error: Identifier 'item' has already been declared (Note that you need plugins to import files that are not JavaScript)

To Reproduce
https://svelte.dev/repl/4e483e1700e04ea79dfd8cb4250d5bd0?version=3.20.1

Expected behavior
Even if there's a bug preventing the entered code from compiling correctly, I should always be able to rewrite the code and try to make the new code compile, and I should always be able to save new versions of the code to my GitHub account.

Information about your Svelte project:
This concerns the REPL live on svelte.dev.

Severity
I may or may not have other bugs to tell you about, but with the REPL in this state, I feel that trying to put together evidence of their existence is more trouble than it's worth.

Additional context
aaaaaaaaaaaaaaaaaaaaaaaaaaaargh

[pushkine]

There is a clash between component name and each_value name in create_each_block

let item = /*item*/ ctx[6];
const item = new Item({ props: item_props, $$inline: true });

[Th0rN13]

This issue can be easily fixed with prefix for component name variable, but need approve prefix,
simple $ may cause a similar problem with stores, so i suggect $c_ (c for component)

[Conduitry]

Here's a stripped down version of the repro

<script>
	const components = [];
</script>

<ul>
	{#each data as item}
		<Item bind:this={components[item]} />
	{/each}
</ul>

This wouldn't actually run anyway because of the missing data and Item, but it does demonstrate that the item that contains the loop variable that's used in the dynamic bind:this isn't getting properly deconflicted with the item that contains the component instance.

[Conduitry]

The bind:this variable should no longer conflict with other variables as of 3.23.2 - https://svelte.dev/repl/4e483e1700e04ea79dfd8cb4250d5bd0?version=3.23.2

[PixievoltNo1]

I'll call that "good enough for my purposes". I'm not sure how I feel about the REPL not being robust enough in the face of Svelte bugs like this one, but as long as there are no such (known) bugs, it doesn't matter.