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.

Supabase works with Vite but not SvelteKit dev mode

See original GitHub issue

Describe the bug

Importing Supabases’s client and refreshing the page shows an error that always looks something like…

500
ENOENT: no such file or directory, open '[project_folder]/node_modules/@supabase/supabase-js/src/index.ts'

Error: ENOENT: no such file or directory, open '[project_folder]/node_modules/@supabase/supabase-js/src/index.ts'

Building and running (npm run build npm run start) works fine, and the client can be used.

Have tested with a normal Vite Svelte app (npm init @vitejs/app) and that works fine.

To Reproduce

npm init svelte@next
npm install
npm install --save @supabase/supabase-js

// index.svelte
import { createClient } from '@supabase/supabase-js'

Reproducible repo

Information about your SvelteKit Installation:

npx: installed 1 in 1.117s

  System:
    OS: macOS 11.2.3
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 939.37 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.15.4 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.10 - /usr/local/bin/npm
  Browsers:
    Chrome: 89.0.4389.90
    Safari: 14.0.3
  npmPackages:
    @sveltejs/kit: next => 1.0.0-next.59 
    svelte: ^3.29.0 => 3.35.0

Chrome

static

Severity

I’m probably doing something stupid here, so sorry if this is a waste of your time. But we want to build a simple-ish web app using SvelteKit and Supabase and this is stopping us.