Development: Make 'ready in' 195ms faster #83628
Merged
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
mischnic
approved these changes
Sep 9, 2025
Tests Passed |
timneutkens
added a commit
that referenced
this pull request
Sep 15, 2025
## What? It's likely that because of the bug in #83628 this logic existed in order to make the tests pass but it adds significant overhead depending on the size of your `app` directory. Since #83628 matches the watcher no longer wait for 200ms it should no longer be needed. Let's see how the tests do with the change.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
What?
The Watchpack instance created defaulted to
aggregateTimeout: 200which causes 200ms of dead time during bootup, affecting theready inlogline.Before:
After:
Next up:
~50ms: Remove loading webpack when Turbopack is used (it still gets required currently fornext.config.js)~110ms: Figure out how to avoid loading TypeScript which is used to checktsconfig.jsonoptions.Closes PACK-5437