-
Notifications
You must be signed in to change notification settings - Fork 30.2k
Time logs: Show full millisecond instead of 1 decimal #88313
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
Merged
timneutkens
merged 1 commit into
canary
from
01-09-time_logs_show_full_millisecond_instead_of_1_decimal
Jan 9, 2026
Merged
Time logs: Show full millisecond instead of 1 decimal #88313
timneutkens
merged 1 commit into
canary
from
01-09-time_logs_show_full_millisecond_instead_of_1_decimal
Jan 9, 2026
+2
−2
Conversation
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
Collaborator
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles: **430 kB** → **430 kB** ✅ -4 B82 files with content-based hashes (individual files not comparable between builds) Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
|
mischnic
approved these changes
Jan 9, 2026
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.

Fix: Remove unnecessary decimal place in millisecond duration formatting
What
Fixed
durationToStringto display whole milliseconds (e.g., "193ms") instead of showing a redundant decimal place (e.g., "193.0ms").Why
The "Ready in X" message was displaying durations like "Ready in 193.0ms" which looks incorrect. The
.0suffix provides no useful information and makes the output look like a bug.How
Changed
.toFixed(1)to.toFixed(0)for millisecond formatting indurationToString(). This aligns with the behavior of the newerdurationToStringWithNanoseconds()function which already uses.toFixed(0)for milliseconds.Before:
✓ Ready in 193.0msAfter:
✓ Ready in 193ms