expecting new escape codes

[mgttt]

let's keep find and fix!

[NoahHahm]

thank you for your hard work.
The discontinuation was very sad because of the debugging usefulness of vm2.

would you be willing to release it on npm in the form of replacing the open source you are working on with the existing vm2 usage method?

[mgttt]

thank you for your hard work.

The discontinuation was very sad because of the debugging usefulness of vm2.

would you be willing to release it on npm in the form of replacing the open source you are working on with the existing vm2 usage method?

I use jevalx() as sandbox for my quants application tools already.

In the meanwhile I am waiting for new escape cases to confirm the methodology (cutting off host object pollution).

The Prove-of-concept parts should be almost done and building npm package is never my priority. I love to code to solve instead of maintenance.