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
Error after SvelteKit update - blocks the entire page when vitePlugin.experimenta.inspector
is enabled
#422
Comments
Can confirm this is reproducible with the error in the node console. Interestingly, |
(vite 3.1.0-beta1) |
@chrisfromredfin Beta is required by the latest SvelteKit - sveltejs/kit#6398 |
Understood; was just confirming version. |
I'm waiting for this to be fixed too. In the meantime if you want to use it, I made (forked off another repo) a limited options workaround months ago because I could use custom z-index because I didn't understand the customInject css option here. It works with 454 though so if you wanna use it until this is fixed, feel free. Super basic, just allows you to enable-disable via meta-shift, enable/disable by default, and add a z-index to the overlays. |
The error is caused by a new feature in vite that appends a |
@dominikg Ok. When will you release this fix? |
@lukaszpolowczyk released in |
@dominikg Is it somehow possible to install this and use it directly before SvelteKit takes |
yes, you can update vite-plugin-svelte. If a regular update doesn't work, you can use an override: https://pnpm.io/package_json#pnpmoverrides (npm and yarn have overrides too, but their config is different) |
Ok, a simple |
Describe the bug
Error after SvelteKit update - blocks the entire page when
vitePlugin.experimenta.inspector
is enabled.Browser console log:
Server terminal log:
Reproduction
npm create svelte@latest my-app cd my-app npm install npm run dev -- --open
svelte.config.js
:To have this effect:
Result: white page in the browser, log in the browser console, log in the server terminal
Logs
No response
System Info
Severity
blocking all usage of vite-plugin-svelte
The text was updated successfully, but these errors were encountered: