This repository was archived by the owner on Nov 20, 2020. It is now read-only.
Reduce synchronous file IO #112
Open
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
This change switches the initial loading of TypeScript into memory from synchronous to asynchronous, and avoids using
fs.existsSyncin the Service Host if we already have the file in memory.For most setups this probably won't make much of a difference, but my project runs in Docker Desktop for Mac, which has a long standing issue with slow, CPU-intensive file IO in mounted folders, so it is necessary to keep build times reasonable. Moving to async for most of the filesystem operations keeps Webpack from pausing each time this loader is invoked.