Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Experimental inspector not found by Vite

See original GitHub issue

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

Issue Analytics

State:
Created a year ago
Comments:17 (14 by maintainers)

Top GitHub Comments

3reactions

bluwycommented, Jul 22, 2022

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

2reactions

dominikgcommented, May 11, 2022

fix released in 1.0.0-next.44

Top Results From Across the Web

vite-plugin-inspect - npm

Inspect the intermediate state of Vite plugins. ... Start using vite-plugin-inspect in your project by running `npm i vite-plugin-inspect`.

Never Search For Svelte Components Again

Hover over elements and open Svelte components in your editor using the Svelte inspector.

vite:vite-plugin-svelte - dependency rfdc does not export ...

I have a monorepo (turborepo, which is basically pnpm workspaces) that contains a sveltekit package, and when I run this command:

Building vite-plugin-svelte-inspector - YouTube

We are going to build a vite -plugin-svelte- inspector, in which you can hover onto any elements and click to jump to the...

Vue 3: Support new <script setup> without ref sugar - YouTrack

Only some cases of vue-global-api are not recognized (WEB-48239) and that's gonna be ... Please file a feature request for vite-plugin-components support.