Problem
The React SDK now reaches the auth server through the adopter's backend (the @seamless-auth/express adapter) over cookies. The discontinued "web mode" (browser → auth server directly) left residual config that points the app straight at the auth server.
.env → VITE_API_URL=http://localhost:5312 (the auth server — legacy/incorrect).env.example → VITE_API_URL=http://localhost:3000/ (the adapter — correct)
The React SDK calls ${apiHost}/auth/<endpoint>, and /auth is the adapter's mount — so the app must target the adapter (:3000), as the example already shows.
Fix
- Update the committed
.env to match .env.example (point at the adapter, :3000).
- Audit other direct-to-auth-server references (
src/lib/runtimeConfig.ts, README/docs) and remove any remaining web-mode assumptions.
Context
Found while building the seamless verify conformance harness; part of cleaning up legacy web-mode residue across the ecosystem.
Problem
The React SDK now reaches the auth server through the adopter's backend (the
@seamless-auth/expressadapter) over cookies. The discontinued "web mode" (browser → auth server directly) left residual config that points the app straight at the auth server..env→VITE_API_URL=http://localhost:5312(the auth server — legacy/incorrect).env.example→VITE_API_URL=http://localhost:3000/(the adapter — correct)The React SDK calls
${apiHost}/auth/<endpoint>, and/authis the adapter's mount — so the app must target the adapter (:3000), as the example already shows.Fix
.envto match.env.example(point at the adapter,:3000).src/lib/runtimeConfig.ts, README/docs) and remove any remaining web-mode assumptions.Context
Found while building the
seamless verifyconformance harness; part of cleaning up legacy web-mode residue across the ecosystem.