StarlingMonkey
StarlingMonkey copied to clipboard
bytecodealliance
The StarlingMonkey JS runtime
This repo currently only contains a somewhat rudimentary README, and no technical and design documentation. We should expand the README itself, but also introduce additional documentation / split some of...
Fetch requests should return a response with headers marked with an `"immutable"` guard, where `check_guard` should always fail. In the Fetch spec it appears this is only ever done for...
Do we have a clear convention in the codebase we use for camel casing versus snake casing?
Running the WPT suite locally I noticed that some of the tests that pass in release mode hit asserts in the debug build. To avoid a proliferation of this, we...
For the test "writer.abort() inside size() should work" In tests/wpt-harness/expectations/streams/transform-streams/reentrant-strategies.any.js.json.
WPT cases regressing in tests/wpt-harness/expectations/compression/decompression-corrupt-input.tentative.any.js.json: * format 'deflate' field ADLER should be error for 255 * format 'gzip' field ISIZE should be error for 1
WPT test regression from tests/wpt-harness/expectations/fetch/api/basic/request-headers-nonascii.any.js.json.
`Response.json` was disabled in the fetch implementation, resulting in WPT regressions, this needs to be uncommented and reimplemented.
ComponentizeJS will run the event loop without interest as a way to ensure that async work is being done. We do this in the post_call for functions so that the...
@guybedford pointed out in [a comment](https://github.com/bytecodealliance/StarlingMonkey/pull/52#discussion_r1644809781_) that the name for a newly introduced phase of a JS app's lifecycle is a bit off. Rather than addressing that in-place, I'm filing...