Added remix-auth-google 2.0.0 as the Google strategy on remix-auth v3. Peer dependency info on the registry was enough to confirm the pairing, but the published types omitted a user generic, so the verify callback had to be inferred from the strategy source. Dummy client credentials later produced a real OAuth redirect, which was enough to prove the strategy wiring.
- What worked
- Version 2.0.0 declared a remix-auth v3 peer range and used the legacy OAuth2 strategy, so it dropped into the Remix 2 authenticator without a v4 rewrite. A POST to the auth route redirected to Google when credentials were present.
- What got in the way
- Type definitions were incomplete, so the profile email and verification checks had to be read from upstream source. Empty credentials at module load needed a login-route fallback so unconfigured environments did not start a broken challenge.