-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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.
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
"Maximum call stack size exceeded" #3218
Comments
This seems to have been introduced in #3150 — when We might be able to get away with something like The safer thing in that case would be to freeze |
I think I ran into this one too. https://svelte.dev/repl/f3cb47560fcd4decbcabfd42e376607b?version=3.6.3 |
Was about to file a new issue, when I stumbled upon this one. My ObservationThis issue occurs when you create a child component using client side api Simple repro scenario😃 https://svelte.dev/repl/d90c6f4e19594c28a4e454b5016570e2?version=3.6.3 |
Hideous hack but works until a fix is released... import { onMount, tick } from 'svelte';
onMount(async() => {
await tick();
new RedChild({ target: document.body })
}) https://svelte.dev/repl/3692752c2bfc4c3f9292bdf84023f852?version=3.6.7 |
I bumped into this as well while trying to fiddle together Svelte and Google Maps API. Reproduction here: https://svelte.dev/repl/80e53830f44c46b895376d1de1c08c93?version=3.12.1 |
Also running in to this issue in > 3.6.3. My issue stems from large documents generated from Markdown with numerous classes (like for highlighting code). Reverting to 3.6.3 does not throw the Maximum call stack size exceeded error. This error is thrown in the |
Same her |
Recursion bug on svelte > 3.6.6 when creating a component using client-side component API. To reproduce: https://svelte.dev/repl/6fbeea34d77f43b9a6d57e1da71668fc?version=3.6.7
This works on 3.5.4.
Error
bundle.js:18532 Uncaught (in promise) RangeError: Maximum call stack size exceededThe text was updated successfully, but these errors were encountered: