aarbitandClaude Sonnet 5
fc37ee5e8b
Adds a dev:lan script (vite --host) so testing on a real device doesn't require permanently changing vite.config.ts's default 127.0.0.1-only binding. Pairs with a small supabaseClient change: when the configured Supabase URL is local (127.0.0.1/localhost), the client now swaps in whatever hostname the page itself was loaded from, so a phone hitting the dev server's LAN IP gets API calls routed to that same IP automatically — no more hand-editing VITE_SUPABASE_URL per network. Never touches a real production Supabase URL. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017DUU6CnxECCDeqDNYJgr5x
28 lines
1.1 KiB
TypeScript
28 lines
1.1 KiB
TypeScript
import { createClient } from '@supabase/supabase-js'
|
|
|
|
const rawUrl = import.meta.env.VITE_SUPABASE_URL
|
|
const anonKey = import.meta.env.VITE_SUPABASE_ANON_KEY
|
|
|
|
if (!rawUrl || !anonKey) {
|
|
throw new Error(
|
|
'Missing VITE_SUPABASE_URL / VITE_SUPABASE_ANON_KEY. Copy .env.example to .env.local and fill them in ' +
|
|
'(run `npx supabase start` then `npx supabase status` for local values).',
|
|
)
|
|
}
|
|
|
|
/** Local Supabase (127.0.0.1/localhost) only: swap in whatever hostname the
|
|
* page itself was loaded from. Lets `npm run dev:lan` + a phone on the same
|
|
* Wi-Fi work without ever hand-editing VITE_SUPABASE_URL — loading the app
|
|
* via the LAN IP makes API calls target that same IP instead of a loopback
|
|
* address the phone can't reach. Never touches a real (non-local)
|
|
* production URL, so this is a no-op outside local dev. */
|
|
function resolveUrl(value: string): string {
|
|
const url = new URL(value)
|
|
if (url.hostname === '127.0.0.1' || url.hostname === 'localhost') {
|
|
url.hostname = window.location.hostname
|
|
}
|
|
return url.toString()
|
|
}
|
|
|
|
export const supabase = createClient(resolveUrl(rawUrl), anonKey)
|