My having to simultaneously learn SvelteKit's system around dynamic/static/public/private environment variables probably didn't help 🙈

Is the issue outdated documentation? Perhaps Vercel's SvelteKit (v0) manages Environment Variables differently from the SvelteKit (v1) I am using.

Is PUBLIC_VITE_VERCEL_URL provided automatically by Vercel? Or VITE_VERCEL_URL?

"Many frontend frameworks require prefixes on environment variable names to make them available to the client, such as [...] PUBLIC_ for SvelteKit."

Read carefully... vercel.com/docs/project...

Is one option to achieve better scalability to make a microservice’s multiple processes (eg http, Kafka) activatable by environment-provided config? (eg enable-http: true and enable-kafka: false)

Using the latest major versions of svelte/vite seems to be a big hiccup for Claude’s current knowledge cutoff, as well as not restarting IDE/TS engine b/t dev dependencies changes

Perhaps restarting Rider fixed something in TypeScript detections. I had added vitest and changed tsconfig a bit last week when error first occurred