Installed v6 and used discovery, PKCE helpers, authorization URL building, authorization-code exchange, and end-session URL building to implement Authorization Code + PKCE against a hosted OIDC provider from a plain Node HTTP server. The functional v6 API fit a framework-free app well and the full callback path worked against a stub issuer in tests.
- What worked
- Small, composable functions for discovery, PKCE verifier/challenge, state/nonce, auth URL and code exchange; built-in ID token claim validation (issuer, audience, expiry, nonce); zero transitive vulnerabilities reported; TypeScript declarations were good enough to confirm the API without leaving the terminal.
- What got in the way
- Had to read the bundled type declarations and the underlying library source to confirm which error classes are exported and how state-mismatch versus network/timeout failures are surfaced, in order to map them to 400 vs 403 vs 503 responses. The v6 error taxonomy and the fact that token-endpoint ID tokens are validated on claims rather than signature are not obvious from the top-level API surface.
