StarlingMonkey
StarlingMonkey copied to clipboard
bytecodealliance
The StarlingMonkey JS runtime
This is an experimental build of StarlingMonkey with GC zealing enabled. The integration tests are run with GC activated every 10 allocations and verify pre write barriers between instructions enabled.
At Fastly we have a pre-defined maximum memory usage for Wasm services. It could be useful to be able to hard-code this limit into the runtime, so that the runtime...
Without a build supporting internationalization we don't get support for regular expressions. For Fastly we fix this with a precompile step to replace in the source text all regular expressions...
Since we usually try and have tracking issues for WPT failures, this is to track the new failures in the recently added tests in https://github.com/bytecodealliance/StarlingMonkey/blob/main/tests/wpt-harness/expectations/fetch/api/request/request-disturbed.any.js.json.
This simple commit takes the existing `Request.clone` implementation and adapts it to work for `Response.clone`. This was done largely as a learning exercise. I did have a question regarding the...
We run a fork of the SpiderMonkey streams implementation on the SpiderMonkey tree. We've discussed various approaches to resolving this in the past, but perhaps the most expedient at this...
There are a few stories here, but this one is a very simple one - inline Fastly's current code modification approach to precompiling regular expressions into something that runs at...
See [https://w3c.github.io/hr-time/#dom-domhighrestimestamp f](https://w3c.github.io/user-timing/) as the required extensions to the `Performance` feature.