feat(browser): Cookie persist $user_state#3135
Merged
dustinbyrne merged 2 commits intomainfrom Feb 23, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Contributor
|
Size Change: +30 B (0%) Total Size: 6.17 MB
ℹ️ View Unchanged
|
b82aa85 to
83d9025
Compare
marandaneto
approved these changes
Feb 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Server-side web frameworks (e.g., Next.js) have no way to know whether a user's distinct ID is anonymous or identified. Comparing
distinct_idto$device_idisn't always reliable considering users can override device ID generation viaget_device_id(). This can lead to client and server disagreeing on user state, and means server-sideidentify()calls can't behave the same as client-side ones.Changes
When using
localStorage+cookiepersistence, add$user_statetoCOOKIE_PERSISTED_PROPERTIESso it's written to the cookie alongsidedistinct_id,$device_id, etc. Server-side code can now read identification state directly from the cookie.This is an additive change -
$user_stateis still persisted to local storage as well.Release info Sub-libraries affected
Libraries affected
Checklist
If releasing new changes
pnpm changesetto generate a changeset file