You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Honestly I don't know what Svelte is doing exactly, but I tried and this bug only happens in 3.25.1 and not in 3.25.0.
I can only tell you what I see. Normally in my sapper app I use $session store which at the moment always only consists of 2 items: { csrfToken: "a random string...", user: { /* a user object */ }}.
Now for some reason, in version 3.25.1, $session gets messed up and csrfToken is gone and user is now the root object. It's like svelte did $session = $session.user somewhere...
Honestly I don't know what Svelte is doing exactly, but I tried and this bug only happens in 3.25.1 and not in 3.25.0.
I can only tell you what I see. Normally in my sapper app I use
$session
store which at the moment always only consists of 2 items:{ csrfToken: "a random string...", user: { /* a user object */ }}
.Now for some reason, in version 3.25.1,
$session
gets messed up andcsrfToken
is gone anduser
is now the root object. It's like svelte did$session = $session.user
somewhere...And it must have happened somewhere between these 2 commits.
The text was updated successfully, but these errors were encountered: