Guy Bedford
Guy Bedford
We just landed a change to StarlingMonkey to support handling the invariants of the monotonic clock by defining an offset based on the difference between the Wizer time monotonic clock...
This adds the support for the dynamic `import.source()` phase from the latest V8, and enabling the tests. //cc @nodejs/loaders
This is a draft PR implementing a Wasm ESM Integration PR for global unwrapping in https://github.com/WebAssembly/esm-integration/pull/104. Opening here as a draft only for feedback and discussion, as it helps to...
### Describe the feature Source phase imports will soon be landing in Node.js (https://github.com/nodejs/node/pull/56919). There is a Babel plugin available at https://babeljs.io/docs/babel-plugin-proposal-import-wasm-source which should allow build tool integration. Would it...
It would be great to support input sources as TypeScript directly that then get converted into JavaScript before running through componentization.
Now that StarlingMonkey is seeking to use runtime environment variables and sockets we might add these to the enable/disable features. Alternatively, we might want a `debugger: true/false` ComponentizeJS option when...
Jco's Node.js implementation could support trailers via the Node.js HTTP API - https://nodejs.org/docs/latest/api/http.html#responseaddtrailersheaders.
For debugging it would be convenient to have a `jco componentize -d all-debug` option which would disable all features except for stdio for debugging.
Suggested by @vados-cosmonic it could be useful to have an option for `jco componentize` to automatically provide a standard WASI world out of the command, proxy and reactor worlds, so...
We should be implementing request isolation for Jco serve, while currently we share the instance execution between requests.