I've not considered using IndexedDB before! Loading a large app generates several GB of data, and extracting that data from the tab is actually a big performanc

I've not considered using IndexedDB before! Loading a large app generates several GB of data, and extracting that data from the tab is actually a big performance issue. Instrumenting a single bundle is possible, but it's common to have some dependency on third-party JS or script tags in the page HTML. Chrome has an experimental request interception API for extensions that allows rewriting the response. I think that would be ideal UX-wise. I'm a bit wary though because that's how I started initially and I ran into a bunch of problems. One issue is running out of memory, the Babel compilation can often take several GB of RAM, and the default V8 memory limit in Chrome is too low.