Hi diggan, Offline mode is an interesting problem. For example, module-fs is 1 part code, 99 parts infrastructure really. We have 3.5TB of installed packages,

Hi diggan, Offline mode is an interesting problem. For example, module-fs is 1 part code, 99 parts infrastructure really. We have 3.5TB of installed packages, stored internally in a content-addressable way, and then exposed as a file system through FUSE. module-fs seems to be something that only becomes powerful when you have ALL packages, thus really having similar performance characteristics of having already installed the packages. The solutions I've seen that try to download packages in the background, etc. don't quite provide this magical "I only need to require it" feeling. Its similar to the issue we have with providing real time-traveling locally: in my experience "time-traveling" has never taken off because its eternally stuck in demo-mode, as all code eventually interacts with the outside world. By snapshotting the entire computer, I think we've pushed this feature over the edge to the point that people use it without realizing it on RunKit, it is of course natural that going back in a REPL also goes back to a previous state. But locally, this feature once again doesn't seem to immediately make sense. At that point the question becomes what part of RunKit would we offer locally? Just the object viewers? I ask this non-rhetorically btw, I am happy to hear what you imagine a "local" RunKit to look like, and if it makes sense we'd certainly consider pursuing it.