Replies: 1 comment
-
The inspector is still classified as experimental and it could interfere with everyday workflows. Given svelte favors stability_over_ surprise and since the inspector is experimental and could clash with common development flows, it makes sense that it's intentionally disabled by default and must be manually enabled (opt-in). The documentation is available at (https://github.com/sveltejs/vite-plugin-svelte/tree/main/packages/vite-plugin-svelte-inspector). This is my usual config: import { svelte } from "@sveltejs/vite-plugin-svelte";
import { svelteInspector } from "@sveltejs/vite-plugin-svelte-inspector";
import { defineConfig } from "vite";
export default defineConfig({
plugins: [
svelte(),
svelteInspector({
toggleKeyCombo: "alt-x",
showToggleButton: "always",
toggleButtonPos: "bottom-left"
})
]
}); If you're saying something like it should be promoted in an easier way so that people can learn about it quicker, I totally agree. Let's submit a PR? 🤜 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Recently I was watching Rich on some video podcast and learned about the inspector feature. We've been using svelte for a year now and had no clue something like this exists, however it'd be really helpful for us.
So I am wondering why it isn't enabled by default? Or at least why it's not there in
svelte.config.js
as a commented piece of config when you create project withnpx sv
?Beta Was this translation helpful? Give feedback.
All reactions