vite-plugin-svelte: Experimental inspector not found by Vite

Describe the bug

Updated to the latest version and tried to set config.experimental.inspector to true in the svelte.config.js file in my SvelteKit project.

Reproduction

Create a new skeleton SvelteKit project and set config.experimental.inspector to true

Logs

vite:resolve 1.77ms /.svelte-kit/generated/root.svelte -> /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/generated/root.svelte +0ms
  vite:load 1.70ms [fs] /.svelte-kit/generated/root.svelte +0ms
  vite:vite-plugin-svelte setting cssHash s-cCKfmRoJfo02 for /.svelte-kit/generated/root.svelte +3s
  vite:vite-plugin-svelte transform returns compiled js for /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/generated/root.svelte +71ms
  vite:import-analysis 0.72ms [0 imports rewritten] .svelte-kit/generated/root.svelte +0ms
  vite:transform 74.83ms /.svelte-kit/generated/root.svelte +0ms
  vite:resolve 0.55ms /.svelte-kit/runtime/paths.js -> /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/runtime/paths.js +128ms
  vite:load 4.32ms [fs] /.svelte-kit/runtime/paths.js +129ms
  vite:import-analysis 0.04ms [no imports] .svelte-kit/runtime/paths.js +54ms
  vite:transform 0.48ms /.svelte-kit/runtime/paths.js +54ms
  vite:resolve 0.60ms /.svelte-kit/runtime/components/layout.svelte -> /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/runtime/components/layout.svelte +12ms
  vite:resolve 0.67ms /src/routes/index.svelte -> /Users/mathiaspicker/Documents/2022/my-app/src/routes/index.svelte +0ms
  vite:load 0.59ms [fs] /.svelte-kit/runtime/components/layout.svelte +9ms
  vite:vite-plugin-svelte setting cssHash s-pdl50zIt_88L for /.svelte-kit/runtime/components/layout.svelte +66ms
  vite:vite-plugin-svelte transform returns compiled js for /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/runtime/components/layout.svelte +6ms
  vite:import-analysis 0.10ms [0 imports rewritten] .svelte-kit/runtime/components/layout.svelte +15ms
  vite:transform 6.58ms /.svelte-kit/runtime/components/layout.svelte +15ms
  vite:load 7.70ms [fs] /src/routes/index.svelte +7ms
  vite:vite-plugin-svelte setting cssHash s-Uap-jPRb-uiE for /src/routes/index.svelte +1ms
  vite:vite-plugin-svelte transform returns compiled js for /Users/mathiaspicker/Documents/2022/my-app/src/routes/index.svelte +3ms
  vite:import-analysis 0.08ms [0 imports rewritten] src/routes/index.svelte +4ms
  vite:transform 3.33ms /src/routes/index.svelte +4ms
  vite:time 240.68ms / +0ms
  vite:load 1.26ms [fs] .svelte-kit/runtime/client/start.js +114ms
  vite:resolve 0.18ms svelte -> /Users/mathiaspicker/Documents/2022/my-app/node_modules/.vite/deps/svelte.js?v=b429f8ae +126ms
  vite:resolve 0.10ms /node_modules/.vite/deps/svelte.js?v=b429f8ae -> /Users/mathiaspicker/Documents/2022/my-app/node_modules/.vite/deps/svelte.js?v=b429f8ae +1ms
  vite:resolve 0.03ms svelte/store -> /Users/mathiaspicker/Documents/2022/my-app/node_modules/.vite/deps/svelte_store.js?v=b429f8ae +0ms
  vite:resolve 0.14ms /node_modules/.vite/deps/svelte_store.js?v=b429f8ae -> /Users/mathiaspicker/Documents/2022/my-app/node_modules/.vite/deps/svelte_store.js?v=b429f8ae +0ms
  vite:resolve 0.33ms ../paths.js -> /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/runtime/paths.js +1ms
  vite:resolve 0.49ms __GENERATED__/root.svelte -> /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/generated/root.svelte +1ms
  vite:resolve 0.24ms __GENERATED__/client-manifest.js -> /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/generated/client-manifest.js +0ms
  vite:resolve 0.16ms /.svelte-kit/generated/client-manifest.js -> /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/generated/client-manifest.js +1ms
  vite:resolve 0.20ms ./singletons.js -> /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/runtime/client/singletons.js +0ms
  vite:resolve 0.18ms /.svelte-kit/runtime/client/singletons.js -> /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/runtime/client/singletons.js +0ms
15:20:08 [vite] Internal server error: Cannot find module '@sveltejs/vite-plugin-svelte/src/ui/inspector/load-inspector.ts'
Require stack:
- /Users/mathiaspicker/Documents/2022/my-app
  Plugin: vite:import-analysis
  File: /Users/mathiaspicker/Documents/2022/my-app/.svelte-kit/runtime/client/start.js
      at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
      at Function.resolve (node:internal/modules/cjs/helpers:108:19)
      at Context.resolveId (file:///Users/mathiaspicker/Documents/2022/my-app/node_modules/@sveltejs/vite-plugin-svelte/dist/index.js:1554:35)
      at Object.resolveId (/Users/mathiaspicker/Documents/2022/my-app/node_modules/vite/dist/node/chunks/dep-e1fc1d62.js:38898:55)
      at async TransformContext.resolve (/Users/mathiaspicker/Documents/2022/my-app/node_modules/vite/dist/node/chunks/dep-e1fc1d62.js:38672:23)
      at async normalizeUrl (/Users/mathiaspicker/Documents/2022/my-app/node_modules/vite/dist/node/chunks/dep-e1fc1d62.js:56884:34)
      at async TransformContext.transform (/Users/mathiaspicker/Documents/2022/my-app/node_modules/vite/dist/node/chunks/dep-e1fc1d62.js:57039:57)
      at async Object.transform (/Users/mathiaspicker/Documents/2022/my-app/node_modules/vite/dist/node/chunks/dep-e1fc1d62.js:38961:30)
      at async doTransform (/Users/mathiaspicker/Documents/2022/my-app/node_modules/vite/dist/node/chunks/dep-e1fc1d62.js:55918:29)
  vite:time 30.07ms .svelte-kit/runtime/client/start.js +121ms
  vite:time 1.53ms /favicon.png +22ms

System Info

System:
    OS: macOS 11.4
    CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
    Memory: 43.46 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 8.1.0 - /usr/local/bin/npm
  Browsers:
    Brave Browser: 101.1.38.111
    Chrome: 101.0.4951.54
    Edge: 101.0.1210.39
    Firefox: 99.0.1
    Safari: 14.1.1
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.40 
    @sveltejs/kit: next => 1.0.0-next.326 
    svelte: ^3.44.0 => 3.48.0

Severity

blocking an upgrade

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 17 (14 by maintainers)

Commits related to this issue

fix: use different way to resolve inspector path (see #330) — committed to sveltejs/vite-plugin-svelte by dominikg 2 years ago
fix: use different way to resolve inspector path (see #330) (#332) * fix: use different way to resolve inspector path (see #330) * test: add tests for inspector with kit and vite templates * fi... — committed to sveltejs/vite-plugin-svelte by dominikg 2 years ago

Most upvoted comments

Error: Invalid options in svelte config. Move the following options into ‘vitePlugin:{…}’: experimental

You need to set config.vitePlugin.experimental.inspector instead. This breaking change was made in 1.0.0 and is documented at https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/config.md#experimental-options

bluwy on Jul 22, 2022

@bluwy Thanks, it works. Phew. All this time I didn’t know what the fault was, I tried other options before, I didn’t know if it was the fault of the configuration or the shortcut or something else. It turns out that both the shortcut and the configuration in part…

The best example to test that everything works:

import adapter from '@sveltejs/adapter-auto';

/** @type {import('@sveltejs/kit').Config} */
const config = {
	kit: {
		adapter: adapter()
	},
	vitePlugin: {
		experimental: {
			inspector: {
				showToggleButton: "always"
			}
		}
	}
};

export default config;

The only distracting downside - VSCode reports problems:

Type '{ kit: { adapter: Adapter; prerender: { default: true; }; browser: { router: false; }; }; vitePlugin: { experimental: { inspector: { showToggleButton: string; }; }; }; }' is not assignable to type 'Config'.
  Object literal may only specify known properties, and 'vitePlugin' does not exist in type 'Config'.

But it still works.

lukaszpolowczyk on Jul 22, 2022

fix released in 1.0.0-next.44

dominikg on May 11, 2022

You’re running pnpm7 which we don’t support yet. You can install it as pnpm add -g pnpm@6. But we’re moving to pnpm7 soon so you can hold your horses for a bit too 😃

bluwy on May 11, 2022

My bad for the confusion! I didn’t catch that it had changed since last time… sorry!

MathiasWP on Jul 22, 2022

The fix worked, @dominikg!

MathiasWP on May 11, 2022