Yeah I thought it might be it getting confused about scopes vs objects again. That’s why I tried x = {}. Honestly, I would’ve thought it would know it’s not a scope from the return you must be adding to run the code in the first place, know what I mean?

Oh maybe you’re doing eval too, which doesn’t use a return–is that it? I’m still thinking in “compilation” terms, the way I do stuff like this. So the JS just stays untouched and depending on the circumstances I just wrap a return (...) around it. But you do a lot of eval stuff, I noticed.

It’s funny, the way I’ve used eval in the past, I do the assignment in the eval. Like, eval("x = 1") which I guess would encourage it to see things as objects/values instead of scopes/code bodies?