Fix client-side relative time calculation for statically generated routes .. #520
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.
Fix #422
Issue:
The
RelativeTime
component displayed incorrect relative time when rendered on statically generated routes since it was computed server-side and did not update based on the client's time.Solution:
RelativeTime
component to compute the relative time on the client side."use client"
directive to ensure that the component runs entirely on the client side.useEffect
anduseState
to calculate and update relative time every minute dynamically.This update addresses the problem by making the relative time always reflect the current time on the client side, providing an accurate user experience.