Benjamin Eckel
Benjamin Eckel
I'm getting this error using asc `0.21.3`: ``` INFO AS210: Expression is never 'null'. : 82 │ this.writeString(str!); │ ~~~ └─ in ~lib/assemblyscript-json/assembly/encoder.ts(82,24) ``` I believe it's because there is...
When doing git push for the first time, I was seeing this error: ``` fatal: bad numeric config value 'updateInstead' for 'receive.denycurrentbranch' in config: invalid unit fatal: Could not read...
Makes a reference to a feature in https://github.com/extism/cli/pull/81 so we should probably resolve that before merging this.
As mentioned in the comments in #68, we do not conform to the full spec for console.log and the other methods on `console`. We should refactor it to be compliant....
I believe the tools we use support windows, so we just need to add windows to our CI and publish workflows: * https://github.com/extism/js-pdk/blob/main/.github/workflows/publish.yml * https://github.com/extism/js-pdk/blob/main/.github/workflows/ci.yml But testing may yield some...
QuickJS does support ESM. Also the quickjs bindings give us a way to eval an ES Module https://docs.rs/quickjs-wasm-rs/3.0.0/quickjs_wasm_rs/struct.JSContextRef.html#method.eval_module We should switch to ESM and maybe even remove CJS support. That...
Currently WASI is required for JS plug-ins. This is for a number of reasons: 1. Some js code like `Math.random()` and `new Date()` requires randomness and clocks respectively 2. The...
We want the JS-PDK to support host functions. They should appear as imports in the JS world. We could come up with some kind of convention like: ```javascript import {host_func1,...
I think polluting the global namespace is not the best decision for the API. And we should consider how this will work from typescript. I'll be doing some research and...
This project is based on an older, but simpler way of building a js toolchain. We are statically compiling everything we need into one wasm file though a series of...