_hyperscript VS OpenXTalk-Community-DPE

It seems to be this one:

https://github.com/bigskysoftware/_hyperscript

https://hyperscript.org/

but no sure it's anything to do with the OP though

You could help hyperscript get to a stable 1.0 by reading docs and writing up some use cases if you know anything about front end web development

If we returned from a function, we step out of it (discussed below). Otherwise, if the command returned a Promise, we await the next command, set cmd to it, notify the event bus and log it with some fancy styles. If the result was synchronous and is a HALT; we stop debugging (as I write this, I'm realizing I should've called continueExec() here). Finally, we commit the kind of code duplication hyperscript is meant to help you avoid, to handle a synchronous result.

It seems they had a GPL version, however they recently discontinued it; a fork of this IIUC seems to be now maintained by a community at: https://github.com/OpenXTalk-org/OpenXTalk-Community-DPE

You can fork OpenXTalk, clone to your machine, then download all the necessary things and try to build it, document what you had to do to overcome the obstacles you faced. If you can build it, then you can go to openxtalk.org and say I did it! Slap that on your resume.

Now the OpenXTalk community are picking up the pieces. The GPLv3 Source code can be forked on Github