Guy Bedford
Guy Bedford
See [https://w3c.github.io/hr-time/#dom-domhighrestimestamp f](https://w3c.github.io/user-timing/) as the required extensions to the `Performance` feature.
This work was implemented for StarlingMonkey's `FetchEvent` in https://github.com/bytecodealliance/StarlingMonkey/pull/220, which we upgraded to in https://github.com/fastly/js-compute-runtime/pull/1145, but this upgrade path did not include the rebasing of our `Event` subclasses to the...
I had to disable the generation insert test in https://github.com/fastly/js-compute-runtime/pull/1120 because it is consistently failing. We should investigate the root cause here and reenable the test to be sure the...
We don't seem to be properly disposing the secret stores created in the integration tests, and as a result we regularly hit the maximum number of secret stores limit. Fixing...
This happens fairly often at this point that docusaurus errors break the deployment. We are supposed to be catching these build errors early in review, but for some reason our...
Work was originally attempted on transform stream support as `bodyTransform` instead of `bodyTransformFn` but that hit some low-level streaming issues which still need to be resolved. We should come back...
Updates to the latest WASI SDK released today.
This implements immutable headers guards for the fetch event request, and any `fetch()` responses. With this change, trying to set a header on one of these will throw a TypeError...
Reposting this draft of the docs refactoring after the reverted deployment in https://github.com/fastly/js-compute-runtime/pull/915. Hopefully we can then try this upgrade again with some more testing.
The outline of the approach is in the fetch-api and request-response portions of this commit in StarlingMonkey - https://github.com/bytecodealliance/StarlingMonkey/commit/ea54ba9f56e16ef1e666f7012b53a2accda31055#diff-bfd29ee9cf4d04102a4d9c40bc041220f5404f7d79e9c69cb1ea8cc4342dada8. Since we fork the fetch and request-response aspects of the API,...