-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
feat: introduced generic time component #5497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@mikeesto I've made a clean PR (just because I accidentally deleted the branch on upstream) (Actually, this branch should have been done on the fork to begin with... but hey, Codespaces default remote was set to upstream) |
📦 Next.js Bundle Analysis for nodejs.orgThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
mikeesto
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why there is a diff for package-lock? Otherwise LGTM.
bmuenzenmeyer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
shanpriyan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
A little audit fix |
Co-authored-by: Michael Esteban <[email protected]>
Description
This PR introduces a simple
Timecomponent that fulfils the specification presented on the issue.It also updates the
enlocale to useen-GBRelated Issues
Fixes #5481