fix: use proper datetime to fix server-side/client-siode mismatch #5479
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.
Description
This PR fixes two issues on the Node.js Website related to rendering.
timeHTML elements by using JavaScript's built-intoLocaleStringfunction. We've forced aUTCtimezone and useen-GBlocale information.theme.tsxmemoization asserts both props as being the same as the comparison only used the MDX content as a comparison, excluding other props such as frontmatter. This should fix Next.js, not "moving" to another page. (The issue is that a re-rendering would not occur).strftimepackage and utilities that are not used anymore.Fixes #5478