-
-
Notifications
You must be signed in to change notification settings - Fork 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
Cannot read properties of undefined (reading 'disable_scroll_handling') #7257
Comments
You need to provide a proper reproduction as instructed by the issue template.
|
I followed instructions from auth-helper After trying every combination I found that if I delete hooks.client.js which only contains import '$lib/db'; it first yells at me with Failed to resolve import "../../src/hooks.client.js" from ".svelte-kit\generated\client-manifest.js". Does the file exist?
Failed to resolve import "../../src/hooks.client.js" from ".svelte-kit\generated\client-manifest.js". Does the file exist? (x2)
3:00:00 AM [vite] Internal server error: Failed to resolve import "../../src/hooks.client.js" from ".svelte-kit\generated\client-manifest.js". Does the file exist?
Plugin: vite:import-analysis
File: V:/xxx/.svelte-kit/generated/client-manifest.js
1 | import * as client_hooks from '../../src/hooks.client.js';
| ^
2 |
3 | export { matchers } from './client-matchers.js'; then when I restart the server, error goes away. |
I can't reproduce this given the instructions. Please provide a repository with the minimum reproducible. |
https://github.com/secretgspot/sveltekit-auth-helper-bug here is the branch with bug presented
watch everything burn! Remove hooks.client.js and bug goes away. |
Remove The problem is that
I feel like the first option is the one that makes the most sense, the others just hide misuse and wouldn't prevent that nebolous error if someone would access the client's methods. |
I also had this issue, and it refused to go, until I removed $app/navigation from a component in $lib. Then once it was resolved, I got $app/navigation back into the same component and I never saw this issue again. Not sure how it was is now magically gone but that makes me nervous about production. I'll aim to move the goto function out of components by propagating events up to be handled by pages under routes instead just to be on the safe side. |
Encountered this too but on refresh it works. Hoping it doesn't appear in prod, as something similar happened in prod (!!!) somewhat recently and idk what caused it. |
This can be reproduced without |
This comment was marked as off-topic.
This comment was marked as off-topic.
I also get this error but when trying to |
I'm also suddenly getting this after a package ( After fiddling around with this, it seems like Vite is doing something funky with "optimizing dependencies" and/or caching. If I close my localhost tab and launch it again in a fresh tab, it eventually works (after a lot of HMR errors and forced reloads)
|
I can reproduce this when adding this to my vite config
Follows previous comment that vite is doing something while building / optimising. |
Describe the bug
Just appeared out of nowhere and bricked the whole app, won't go away no matter what. Tried deleting node_modules + .svelte-kit then reinstall and still there.
Reproduction
https://github.com/secretgspot/sveltekit-auth-helper-bug
installed sveltekit latest,
installed supabase-js v2,
installed auth-helpers-sveltekit
Logs
No response
System Info
Severity
blocking all usage of SvelteKit
Additional Information
No response
The text was updated successfully, but these errors were encountered: