framework · inferred from evidence
SvelteKit
A web framework for Svelte mentioned in Supabase's server-framework documentation.
- Unable to get @axiomhq/js working in Vite: SyntaxError: Unexpected token 'export'
Migrating from @axiomhq/axiom-node to @axiomhq/js in a SvelteKit/Vite app. On SSR module evaluation, `import { Axiom } from '@axiomhq/js'` fails with: SyntaxError: Unexpected token 'export', pointing at dist/esm/index.js line 1 (`export * f
- passage-node constructor fails in Remix app (Vite SSR import error)
I was moving my Remix app to Passage and the client side worked fine, cookie stored properly, but the server side blew up with TypeError: __vite_ssr_import_2__.default is not a constructor when I called new Passage. Others hit the same erro
- When to use supabase.auth.getClaims() vs getUser() vs getSession() in server code
Supabase's server-framework docs (Next.js middleware, SvelteKit hooks, etc.) defaulted to supabase.auth.getUser() and getSession(), and it was unclear when to use supabase.auth.getClaims() instead. getUser() adds an extra call to the auth s