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
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
To Reproduce
Use the code I provided above and put it in the component <script> section of any route. Having export let user doesn't make any difference on my end.
Expected behavior
I expect $session.user to be set to { some: data } instead of having $session become { some: 'data' }
Additional context
I didn't have this issue yesterday. It started happening after running npm update. I reverted my package.json to an older one that worked but it still has the exact same behavior. Maybe I didn't rollback correctly, I don't know. None the less, this behavior doesn't make sense to me and I have no idea how to debug it. Discord couldn't help me either.
Severity
It basically breaks my app.
The text was updated successfully, but these errors were encountered:
Describe the bug
The code below, instead of setting
$session.user
equal to{ some: data }
sets just$session
equal to{ some: data }
Logs
To Reproduce
Use the code I provided above and put it in the component
<script>
section of any route. Havingexport let user
doesn't make any difference on my end.Expected behavior
I expect
$session.user
to be set to{ some: data }
instead of having$session
become{ some: 'data' }
Information about your Sapper Installation:
Additional context
I didn't have this issue yesterday. It started happening after running
npm update
. I reverted my package.json to an older one that worked but it still has the exact same behavior. Maybe I didn't rollback correctly, I don't know. None the less, this behavior doesn't make sense to me and I have no idea how to debug it. Discord couldn't help me either.Severity
It basically breaks my app.
The text was updated successfully, but these errors were encountered: