Skip to content

Broken page with Svelte 5: uncaught effect_update_depth_exceeded #13768

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
probablykasper opened this issue Oct 21, 2024 · 5 comments · May be fixed by #16165
Open

Broken page with Svelte 5: uncaught effect_update_depth_exceeded #13768

probablykasper opened this issue Oct 21, 2024 · 5 comments · May be fixed by #16165
Assignees
@dummdidumm

Comments

@probablykasper
Copy link

probablykasper commented Oct 21, 2024 •
edited
Loading

Describe the bug

Upgrading from Svelte 5 (without making any code changes) resulted in an infinite effect_update_depth_exceeded error

Reproduction

https://svelte.dev/playground/48f838c2c37d447faa909ea9bd50d90f?version=5.1.6

Logs

Error: effect_update_depth_exceeded Maximum update depth exceeded. This can happen when a reactive block or effect repeatedly sets a new value. Svelte limits the number of nested updates to prevent infinite loops

Severity

blocking an upgrade

Additional Information

No response
@eltigerchino eltigerchino transferred this issue from sveltejs/kit Oct 22, 2024
@knd775
Copy link

knd775 commented Oct 22, 2024

Can confirm. This is also happening to a number of our selects.

@Travja
Copy link

Travja commented Oct 23, 2024

Dependabot upgraded our project from 4.2.19 to 5.0.5 and I'm seeing this issue as well.

@knd775
Copy link

knd775 commented Oct 23, 2024

It only happens when the component isn't in runes mode.

@Travja
Copy link

Travja commented Oct 26, 2024 •
edited
Loading

I've been trying to make sure that everything is properly updated to Svelte 5 syntax for runes and everything but am still facing the issue. It's possible that I have more updating to do. My project is fairly complex with a lot of moving parts.

Edit: looks like I got things figured out.

@probablykasper
Copy link
Author

@dummdidumm Hey, wondering if this bug could be looked at (it's blocking me from upgrading to Svelte 5). Not sure if it fell through the cracks

@dummdidumm dummdidumm self-assigned this Apr 10, 2025
@raythurnvoid raythurnvoid linked a pull request Jun 15, 2025 that will close this issue
Open
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dummdidumm dummdidumm

Labels
None yet
Projects
None yet
Milestone
No milestone
4 participants
@knd775 @Travja @dummdidumm @probablykasper