Repository navigation
Tracking issue: compile cache #52696
Description
Activity
Avoid UTF8 transcoding by directly reading the source code as buffer from disk (this needs to dance with CJS loader monkey patching)
FWIW I think loaders/require hooks are probably very common in dev and pretty rare in production (where compile cache has the most value) but that's just intuition.
Reacted by Moshe Atlowand pretty rare in production
I would think it's the opposite for tracing agents - although they usually don't care about the source code (except the current loaders built on top of the off-thread hooks like import-in-the-middle that are forced to do a hacky analysis of the source code, which is why I am proposing a in-thread
link()hook for them in nodejs/loaders#198 to not have to do this).Reacted by James SumnersAlso, speaking of loader hooks, I think we need to convert the CJS loader to pass buffers around regardless for future binary file loading support (for example if the custom loader wants to support loading wasm, or zip, or anything that's not stored as uh, bytes encoded in UTF8 on disk).
(Now I am spamming this tracking issue but) after some looks into existing monkey patching usages in popular packages (or I did a GitHub code search) I think the most prioritized item should be an API for packages to turn this on programmably. I don't have a great idea about how this API should look like though, so ideas welcomed. (Maybe
process.enableCompileCache(dir)with some re-entrancy guards would be good enough, or maybe it's a terrible idea to make it per-thread because packages can step on each other's toes?).Other hashing algorithm
xxhash by the creator of ztsd seems a good no-crypto hash algorithm.
Reacted by Toni Villena and Joyee Cheung- added a commit that references this issue
on Sep 12, 2025 - added a commit that references this issue
on Sep 12, 2025 - added a commit that references this issue
on Oct 31, 2025 - added a commit that references this issue
on Nov 18, 2025 This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Follow up to #47472 . Some items that can be investigated:
NODE_COMPILE_CACHEenvironment variable: module: implement NODE_COMPILE_CACHE for automatic on-disk code caching #52535--experimental-transform-types#54741