Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -236,3 +236,5 @@
- Bind socket-read test listeners to IPv4 loopback so `localhost` address-family differences do not cause connection-refused failures in containers.

- Wake idle event loops when the engine schedules immediate garbage-collection work, including requests from collector threads, without extending worker lifetime.

- Update the ten checksum-pinned [OpenClaw WebKit archives](https://github.com/openclaw/WebKit/releases/tag/autobuild-cb8d6f202b5a396caa204ee1bb75d78175aa841a) for passive-collector wakeups and budgeted-worker collection cadence, preserving full-GC heap-limit confirmation and the immediate-timer companion.
2 changes: 2 additions & 0 deletions docs/runtime/nodejs-compat.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -310,6 +310,8 @@ Valid `vm.Script` cached data is accepted when JSC runs without a JIT. Validatio

Immediate engine GC timers wake idle workers when scheduled. These native wakeups do not keep a worker alive.

Budgeted workers can use young-generation collections within their managed heap budgets; full collections still confirm heap-limit exhaustion. Synchronous GC wakes a passive collector even while another heap occupies the shared helpers.

File workers select `--require` and `--import` preloads from their environment independently of `execArgv`. Explicit `env` or `execArgv` options re-read the worker's `NODE_OPTIONS` and `BUN_OPTIONS` before applying the selected CLI arguments. `execArgv: []` removes CLI preloads while environment preloads still apply. Require preloads run before import preloads.

`MessagePort.emit()` and `parentPort.emit()` preserve the emitted value for Node listeners. Web listeners receive `MessageEvent` objects for `message` and `messageerror`, and `CustomEvent` objects for other events.
Expand Down
Loading
Loading