You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.
At the moment the quickjs runtime comes up pretty empty. That means even basics such as setTimeout are missing. This is because we are not compiling in quickjs-libc.c which unfortunately does not actually work in a WASM environment at the moment. It's probably also a better idea to actually set up a tokio current thread runtime or similar and have that be hooked up with the engine.
The following APIs should be provided:
Promise
setTimeout
setImmediate
clearTimeout
console
JSON
The text was updated successfully, but these errors were encountered:
There are actually quite a few arguments for not including the ability to schedule something into the mainloop for the use in our pipeline so for now I would book this as "revisit later".
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment the quickjs runtime comes up pretty empty. That means even basics such as
setTimeout
are missing. This is because we are not compiling inquickjs-libc.c
which unfortunately does not actually work in a WASM environment at the moment. It's probably also a better idea to actually set up a tokio current thread runtime or similar and have that be hooked up with the engine.The following APIs should be provided:
Promise
setTimeout
setImmediate
clearTimeout
console
JSON
The text was updated successfully, but these errors were encountered: