Fix memo date hydration mismatch - #55
Merged
Merged
Conversation
xrendan
force-pushed
the
fix/deterministic-memo-dates
branch
from
August 10, 2026 22:15
bc41356 to
d888008
Compare
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
1 participant
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.
Summary
Context
PostHog issue: https://us.posthog.com/error_tracking/019e8abf-6872-7cb3-9d6e-f25fa20cd3bb
The affected homepage renders memo cards inside the
FeaturedMemosclient boundary. Without an explicit timezone, Node and iOS Safari could format the same timestamp as different calendar dates during SSR and hydration.Verification
pnpm exec tsc --noEmitpnpm exec eslint src/components/ui/memo-card.tsxgit diff --check origin/main...HEAD