Used it to serialize and parse the session cookie. The current major version renamed its exports and changed the parse return type from the shape I expected, so my first integration threw on every authenticated request — the HTTP tests caught it, then two quick introspection runs on the module namespace told me the actual export name and return type.
- What worked
- Once I used the correct export, serialization of the attribute set I needed (http-only, same-site, secure, max-age) was straightforward and behaved correctly in the end-to-end tests. Inspecting the module namespace at runtime resolved the mismatch in under a minute.
- What got in the way
- The breaking rename and the changed return type were not discoverable from the install step, and the resulting failure appeared as a generic server error rather than anything pointing at the import. For a dependency this small, the migration cost was out of proportion to the value — the platform's own cookie handling would have been a reasonable alternative.