1
I Use This!
Low Activity

Commits : Listings

Analyzed about 9 hours ago. based on code collected 1 day ago.
Jun 11, 2025 — Jun 11, 2026
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
The `JS_Utf8BufferIsCompilableUnit` issue got fixed within 24 hours after reporting it in the firefox Matrix chat, updating SpiderMonkey to mozilla-central tip More... almost 2 years ago
chore(CI): use the Windows 2022 runner entirely More... almost 2 years ago
docs(CI): explain why we need Windows 2022 runner to build SpiderMonkey More... almost 2 years ago
fix: crash in Debug Build of SpiderMonkey More... almost 2 years ago
chore: fix uncrustify build on Windows More... almost 2 years ago
chore(CI): switch to the Windows 2022 runner to build SpiderMonkey More... almost 2 years ago
fix: in SpiderMonkey's `js/src/configure` script, the `--without-system-zlib` option is not available on Windows More... almost 2 years ago
chore: re-enable Windows builds More... almost 2 years ago
Merge branch 'Xmader/ci/fix-windows-uncrustify' into Xmader/chore/moz-central More... almost 2 years ago
chore: fix uncrustify build on Windows More... almost 2 years ago
fix: `JS_Utf8BufferIsCompilableUnit` would still generate exception for invalid inputs More... almost 2 years ago
fix: pmdb's debugger global object now requires to be in a cross-compartment wrapper to use on the main global object More... almost 2 years ago
fix: `tests/js/commonjs-modules.bash` needs a much longer timeout if we build in debug mode More... almost 2 years ago
fix: `timers-force-exit.simple` to have a longer timeout because 2s is not enough for the teardown in debug mode More... almost 2 years ago
fix: update the test suite to reflect the change that property access errors now says `TypeError: can\'t access property` More... almost 2 years ago
WIP: bug in defining the debugger global object, disable pmdb for now More... almost 2 years ago
fix: `JSErrorReport`'s `filename` property should now be a `JS::ConstUTF8CharsZ` instead of a pure `char*` after upgrading SpiderMonkey to mozilla-central tip More... almost 2 years ago
fix: forcibly enable FinalizationRegistry and iterator helpers More... almost 2 years ago
feat: SpiderMonkey now supports APIs for one-byte latin1 JSExternalStrings More... almost 2 years ago
fix: `setWeakRefsEnabled` and `setIteratorHelpersEnabled` no longer present on `JS::RealmCreationOptions` after upgrading SpiderMonkey to mozilla-central tip More... almost 2 years ago
fix: `JSErrorReport`'s `filename` property is now a `JS::UniqueChars` (`mozilla::UniquePtr<char[], ...>`) instead of a pure `char[]` after upgrading SpiderMonkey to mozilla-central tip More... almost 2 years ago
fix: for `JS::NewExternalArrayBuffer`, the custom destructor is now wrapped in a `mozilla::UniquePtr` instead of passing it directly to the function More... almost 2 years ago
fix: extending `JS::JobQueue` class now needs to implement the `isDrainingStopped` virtual method after upgrading SpiderMonkey to mozilla-central tip More... almost 2 years ago
fix: passing a column number offset for JS source code now requires the use of `JS::ColumnNumberOneOrigin` class after upgrading SpiderMonkey to mozilla-central tip More... almost 2 years ago
chore: WIP: ignore Windows builds for now More... almost 2 years ago
chore: change back to the tip commit More... almost 2 years ago
chore: force the build system not to verify the macOS SDK version More... almost 2 years ago
Revert "chore: try SpiderMonkey 120" More... almost 2 years ago
Revert "chore: switch back to SpiderMonkey 115 should be fail-proof" More... almost 2 years ago
chore: rollback More... almost 2 years ago