he/him 
Not enough JS tools have cachable artifacts. Warm starts could be so much faster.
Show this thread
-
Even better if those artifacts are per-file, and contain no absolute paths. Shared caches! Critical for scaling for a large company/codebase. A cache shared between all dev machines. Not a capability you see often with open source JS tooling.
Show this thread
Here’s my plug: I had to think about this from the beginning with Rome. Having workers was a good constraint because all messages had to be serializable. Good boundary for thinking about these artifacts.
