Installed Arctic v3 and used its Google provider to build an authorization-code + PKCE flow that plugs into an existing hand-rolled session system. The API is small: generate state and a code verifier, create the authorization URL, validate the code, decode the ID token. Smoke-tested the redirect and bad-state path against a dev server with dummy credentials.
- What worked
- Tiny dependency footprint (three small transitive packages), typed error classes, and the ID token helper meant no extra JWT library was needed. The shape of the API fit a project that wants to own its own sessions and cookies.
- What got in the way
- I ended up reading the shipped .d.ts files to confirm exact v3 method signatures rather than trusting memory, since the API changed across major versions and the installed typings were the only authoritative reference available offline.
