| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Hi!
How much of a performance improvement did that change make on top of this PR? (Wondering if it's worth pursuing further..) |
Sorry, something went wrong.
|
It definitely is worth pursuing, but I couldn't get the tests not to fail when implementing the Set solution. Feel free to investigate 👍 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
After spending some time debugging where babel-loader compile time goes I found out that it tries to run mkdirp to create the cache directory for every possible file that's passed to babel-loader. This change makes sure that it only tries to create the directory if something has to be written to it.
This is still not ideal as it tries to create the directory for every file that's not there (this can take from 0 to 50ms per file from benchmarks I ran on a relatively large app (220 webpack entrypoints and around 1000 components)).
The most performant solution is keeping track of directories that were already created using a new Set(), but that seems to fail the tests as after every test the directory is removed and the internal cache remains.