Yup. The time travel stuff is somewhat transparent and hard to talk about. If you think of the document as a .js file, than it is pretty easy to reason about what will happen. Things are just executed in order. The magic is that we don't have to re-execute a bunch of stuff every time just to get to your actual change.

> The time travel stuff is somewhat transparent and hard to talk about.

Wouldn't that mean it's opaque, since we can't see see into it?

PS. That's picky. This is a rad project and I love the time travel & the 'requiring packages automatically installing them' feature too.

Do you override 'require('fs')' or do you do some magic at the OS level ?

We use docker pretty extensively, and so between each code cell we can evaluate the layered filesystem docker provides for changes and save them.

Good, thanks.