@WiFi77 would it make sense to expose an xworker able to terminate() the worker, same way you would terminate a terminal? Please note that won't be necessarily created out of the box (it's lazy loaded on first run) so you'd need to script.xworker?.terminate() eventually, and that means the editor won't be able to run anymore. This is a feature asking for troubles though but if you really know what you are doing, I think we should provide a way to terminate the worker or maybe we could provide a kill() method to that script that will automatically destroy the editor too, but that might be a bit too obtrusive if we remove nodes out of the blue.

Thoughts? /cc @ntoll