Thanks @big-soccer-75859, please do let us know if you see anything not captured by that bug. Generally speaking, importing on the inside of a function should work around most (all?) of these issues. I realize, however, that this isn't idiomatic and what we would all write by default, so we will be spending some time next week discussing what to do here. Earlier on, we serialized modules differently -- so they led to actual requires during deserialization -- and it feels like this would address all of the issues we are seeing. Stay tuned and thanks for the great feedback!