JavaScript boy and “lovely thoughtleader” 
he/him 
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Also more context on what is actually being “memory cached”: Only the formatted code and errors for each file are cached. We are still computing all the possible files, filtering them with globs, talking to the workers to get their cached value, and printing it all.
Biggest way I make this so fast is that I’ve written all the code, so it’s pretty easy for me to identify inefficiencies. I can change on piece to fit the performance characteristics of another (ie. changing API, integrating caches etc)
Also to be clear, there are some libraries that I've forked. Notably mozilla/source-map and babel-parser. Both for some of the reasons listed, changing the API and cache integration. Having everything be 100% typed, tested, and in the same codebase gives me a lot more confidence.
The test here is after someone else takes ownership of the code does performance stay high. The only way I have seen this happen is by performance conformance tests being treated as pass/fail signs in presubmit.
Yeah, planning on implementing benchmarking into the testing framework. Making benchmarks act as any other test except they work serially (even across workers) to reduce measurement variance. Maybe even something to save the last time, and fail if the delta is >X%.
Oh man, I wish. I'm working on caching for @parceljs and it's tough working with tools designed without persistent caching in mind. I'm hoping that my abstraction will encourage more cacheable tooling though, allowing Parcel to improve over time.
Would love some feedback when it's more ready 
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
