Svelte 5: Several circular dependencies in client runtime modules

[Conduitry]

Describe the bug

Not a bug, per se, but there are several circular dependencies among various files in the browser runtime. Here are a few that I observed in a project. There may be others that present themselves if you use more of Svelte's runtime.

svelte/src/internal/client/each.js -> svelte/src/internal/client/render.js -> svelte/src/internal/client/transitions.js -> svelte/src/internal/client/each.js
svelte/src/internal/client/proxy/readonly.js -> svelte/src/internal/client/proxy/proxy.js -> svelte/src/internal/client/proxy/readonly.js
svelte/src/internal/client/render.js -> svelte/src/internal/client/transitions.js -> svelte/src/internal/client/render.js
svelte/src/internal/client/runtime.js -> svelte/src/internal/client/block.js -> svelte/src/internal/client/runtime.js
svelte/src/internal/client/runtime.js -> svelte/src/internal/client/proxy/readonly.js -> svelte/src/internal/client/proxy/proxy.js -> svelte/src/internal/client/runtime.js
svelte/src/internal/index.js -> svelte/src/internal/client/custom-element.js -> svelte/src/legacy/legacy-client.js -> svelte/src/internal/index.js

If it comes down to it, I suppose we could suppress these warnings in our official tooling, but it would be nicer not to have the cycles at all if possible, for people with a more homegrown setup.

Reproduction

Attempt to bundle a Svelte 5 app directly with Rollup rather some other higher level tool, without suppressing CIRCULAR_DEPENDENCY warnings, and observe them at build time.

Logs

No response

System Info

n/a

Severity

annoyance

[josdejong]

I encounter the following circular dependencies:

node_modules/svelte/src/internal/client/reactivity/effects.js -> node_modules/svelte/src/internal/client/runtime.js -> node_modules/svelte/src/internal/client/reactivity/effects.js
node_modules/svelte/src/internal/client/reactivity/effects.js -> node_modules/svelte/src/internal/client/runtime.js -> node_modules/svelte/src/internal/client/dev/ownership.js -> node_modules/svelte/src/internal/client/reactivity/effects.js
node_modules/svelte/src/internal/client/runtime.js -> node_modules/svelte/src/internal/client/dev/ownership.js -> node_modules/svelte/src/internal/client/runtime.js
node_modules/svelte/src/internal/client/runtime.js -> node_modules/svelte/src/internal/client/reactivity/sources.js -> node_modules/svelte/src/internal/client/runtime.js
node_modules/svelte/src/internal/client/runtime.js -> node_modules/svelte/src/internal/client/reactivity/deriveds.js -> node_modules/svelte/src/internal/client/runtime.js

[Aristocrates201]

I encounter the following circular dependencies after upgrading from svelte 4 to svelte 5:

src/main.js → public/build/bundle.js...
(!) Circular dependencies
node_modules/svelte/src/internal/client/runtime.js -> node_modules/svelte/src/internal/client/reactivity/effects.js -> node_modules/svelte/src/internal/client/runtime.js
node_modules/svelte/src/internal/client/reactivity/sources.js -> node_modules/svelte/src/internal/client/runtime.js -> node_modules/svelte/src/internal/client/reactivity/effects.js -> node_modules/svelte/src/internal/client/reactivity/sources.js
node_modules/svelte/src/internal/client/dom/operations.js -> node_modules/svelte/src/internal/client/dom/hydration.js -> node_modules/svelte/src/internal/client/dom/operations.js
...and 13 more

I don't know whether it makes a difference for this purpose, but my project is an electronjs app.