Installed remix-auth to own cookie sessions and authenticate the private board with a Google strategy. Version selection was the hard part: a documented-looking 3.7.1 release did not exist, v4 would have dropped managed sessions, and only 3.7.0 paired cleanly with the Remix 2 app. After that pin, Authenticator-based checks and redirects were straightforward.
- What worked
- Once 3.7.0 was installed, session-backed isAuthenticated checks and login error handling were clear from the shipped type definitions and matched the cookie session approach already chosen.
- What got in the way
- The first install targeted a non-existent 3.7.1 and failed peer resolution. Distinguishing v3 from v4 and confirming the last real v3 release required registry version listing rather than the package docs alone.
