-
Notifications
You must be signed in to change notification settings - Fork 184
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
TypeError: Cannot read properties of undefined (reading 'default')
after upgrading to 2.2.0
#262
Comments
2.2.0
TypeError: Cannot read properties of undefined (reading 'default')
after upgrading to 2.2.0
|
svelte: 4.2.2 |
Can you please try latest version of |
This same bug in |
@motzel Could you please have look, Thanks |
This line in the source code is completely different. The only places where the svelte-routing/src/Router.svelte Line 52 in 2673fe7
Line 33 in 2673fe7
Line 100 in 2673fe7
and none of them were changed in my PR. My guess is that the problem is in either of the last two, because the @Saibamen Could you prepare a minimal example in which this bug appears? Or just replace |
Full stacktrace (version 2.2.0):
|
@motzel: I added |
@Saibamen This is all the way impossible, because there is no other reading of |
Oh, I didn't notice that you already added the full stacktrace (I'm on mobile now), sorry |
@Saibamen I have prepared a minimal example of svelte-routing (based on the documentation from the readme). It uses svelte-routing@2.2.0 and svelte@4.2.2, just like your project. Could you fork it and break it in the same way as in your project? |
@motzel: Working version: https://github.com/Saibamen/svelte-routing-example/tree/2-1-0_working Upgrade |
Thanks! I'll check it out today after work (~in 8h) |
at Router.svelte:45:28
Line 45:
if (default_slot) default_slot.c();
This runtime error was introduced in svelte-routing 2.2.0.
Version 2.1.0 is OK.
Related: #258
The text was updated successfully, but these errors were encountered: