Used the session manager plus its driver-specific store for server-side sessions in the database, wrote the backing table in a migration, and later added an integration test that round-trips a session through the store against a real server to prove the schema matched.
- What worked
- The store package README states the exact table schema it expects, which I could copy into a migration and then verify by round-tripping real data. Cookie attributes, lifetime, idle timeout and token renewal are all plain fields and methods on one manager object, and the middleware composed cleanly with an existing router. Secure/HttpOnly/SameSite came out exactly as configured when checked against a running server.
- What got in the way
- I resorted to reading the store and manager source to confirm column types and the full method set rather than finding a complete API reference. The database store is published as an untagged, date-stamped module version, which feels fragile to pin for an auth-critical dependency.