Skip to content

chore(deps): bump @morojs/engine from 1.1.13 to 1.1.18 - #35

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/morojs/engine-1.1.17
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/morojs/engine-1.1.17

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @morojs/engine from 1.1.13 to 1.1.18.

Release notes

Sourced from @​morojs/engine's releases.

v1.1.18

@​morojs/engine 1.1.18

A request-body and WebSocket release. Nothing on the wire changes and no export is added, removed or renamed; what changes is how many times a body's bytes are copied between the socket and the handler, how much memory an upload holds while it is arriving, and what one WebSocket read costs above the frames it carries.

Bodies collected where they land

A request JS will see has its head parsed from the read buffer in place, as engine-answered requests already had; it is no longer copied into the connection's buffer first. A Content-Length body is collected straight into the body buffer: what arrived with the head is copied once, and every later read appends to that buffer directly. The body used to accumulate in the connection's read buffer and be copied out of it whole once complete, so a 10 MB upload held 20 MB at its peak and was copied twice; it now holds 10 MB and is copied once. Chunked bodies, pipelined follow-ups and every limit and error path keep their behaviour; seven regression tests pin the paths that differ from the one-read case.

Handed to JS without a copy

getBody() no longer copies the body into a fresh ArrayBuffer. The collected bytes become the buffer's backing store as they are, freed when JS lets go of it, and a second call during the same request returns the same storage rather than a second copy. The storage is released when the request finishes, so nothing stays pinned to an idle keep-alive connection; a body the handler kept lives on in JS alone.

The hand-over deliberately uses a plain V8 backing store rather than node::Buffer::New with a free callback. That form books the bytes as external memory, and a lean handler taking 10 KB bodies at tens of thousands a second hit the 64 MB external budget every few thousand requests, which V8 answers with a full mark-compact: a tenth of the worker's CPU went to marking. A note for anyone measuring such a path: V8 frees these buffers in the scavenge, and a handler that allocates almost nothing on the JS heap never triggers one, so the buffers are reclaimed by the major collector instead. That is V8's accounting, not the engine's, and it is unchanged by this release.

One callback scope per WebSocket read

Every frame used to enter JS through its own Node callback scope: a context enter and exit, an async-hooks push and pop, and a microtask checkpoint, per frame. A read now opens those once and delivers all of its frames inside them; per frame that leaves a handle scope and a TryCatch. The microtasks a handler queues run when the read's scope closes, after its last frame and before the next read, which is when Node's own 'data' callback runs them

... (truncated)

Changelog

Sourced from @​morojs/engine's changelog.

Changelog

One file per release in https://github.com/Moro-JS/engine/blob/main/changelog; the GitHub Release for a tag carries the same text. Newest first.

  • 1.1.21 — documentation release: README and roadmap brought up to date; no source change.
  • 1.1.20 — TLS on a bundled BoringSSL (two binaries per ABI; Node's OpenSSL selected by itself under FIPS or an OpenSSL config, or with MORO_ENGINE_TLS / selectTls()); the bundled copy follows upstream by a scheduled release; probe().tls.
  • 1.1.19 — HTTP/2 (ALPN and prior knowledge, the engine's own implementation; h2spec 146/146); TLS replies written straight to the socket, AES-128-GCM preferred by default; request bodies as heap strings or lent buffers (getBodyType, getBodyText, getBodyLent), body buffers pooled per loop; epoll: each ready socket served once per loop turn.
  • 1.1.18 — request bodies collected straight into the body buffer (one copy, half the peak memory of an upload); getBody() hands the bytes over without a copy; one callback scope per WebSocket read.
  • 1.1.17 — TLS on the engine's own BIOs (one copy in, one append out, no zeroing); bodies over 8 KiB encrypted from the caller's bytes; ciphertext scratch kept up to 1 MiB.
  • 1.1.16 — wsSend() borrows its payload (the backpressure shed is deferred); ASCII text frames as one-byte strings; TLS record buffers released again.
  • 1.1.15 — WebSocket upgrades performed by the engine (setWsAutoUpgrade, handshake accessors); frames built in the cork buffer; TLS record buffers kept between records.
  • 1.1.14 — WebSocket replies corked per read (one write for a pipelined batch); one ciphertext buffer per loop on the TLS write path.
  • 1.1.13 — epoll transport: the service order is selectable (grouped, arrival, or measured auto); the default is unchanged.
  • 1.1.12 — epoll transport serves each loop turn's sockets grouped by peer CPU.
  • 1.1.11 — epoll transport on one epoll_wait per loop turn; engine-answered routes parsed and routed per request.
  • 1.1.10 — engine-answered routes parsed in place and framed from a prepared head; epoll transport the Linux default; request-registry fix.
  • 1.1.9 — parameter routes (setParamRoute, clearParamRoutes).
  • 1.1.8 — TLS release, one new native function.
  • 1.1.7 — correctness release with one transport improvement.
  • 1.1.6 — the JS boundary: prepared templates, static routes, V8 fast API calls, worker-thread teardown, PGO builds.
  • 1.1.5 — hot-path and memory-headroom audit.
  • 1.1.4 — correctness hardening from the code-quality audit.
  • 1.1.3 — security hardening, third-party audit closed.
  • 1.1.1 — hot-path performance patch.
  • 1.1.0 — pipelined response corking, zero-allocation hot path.
Commits
  • 1e70d45 chore: release v1.1.18
  • d3cce33 One Node callback scope per WebSocket read
  • 8ff555f Request bodies collected once and handed to JS without a copy
  • f4f2ccd chore: release v1.1.17
  • 141f92b TLS on the engine's own BIOs; large bodies encrypted in place
  • ec67d7e chore: release v1.1.16
  • e0eee11 chore: update changelog for v1.1.16 release with wsSend() improvements and TL...
  • e1b6c3a chore: release v1.1.15
  • 5009cbf v1.1.15
  • db15d89 ci: update macOS runner from 14 to 15 in CI and release workflows
  • Additional commits viewable in compare view

@dependabot
dependabot Bot requested a review from M-Chris as a code owner November 9, 2026 03:09
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 9, 2026
@dependabot dependabot Bot changed the title chore(deps): bump @morojs/engine from 1.1.13 to 1.1.17 chore(deps): bump @morojs/engine from 1.1.13 to 1.1.18 Nov 12, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/morojs/engine-1.1.17 branch 2 times, most recently from b91a84a to a49cea8 Compare November 12, 2026 17:12
Bumps [@morojs/engine](https://github.com/Moro-JS/engine) from 1.1.13 to 1.1.18.
- [Release notes](https://github.com/Moro-JS/engine/releases)
- [Changelog](https://github.com/Moro-JS/engine/blob/main/CHANGELOG.md)
- [Commits](Moro-JS/engine@v1.1.13...v1.1.18)

---
updated-dependencies:
- dependency-name: "@morojs/engine"
  dependency-version: 1.1.17
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/morojs/engine-1.1.17 branch from a49cea8 to 592503f Compare November 14, 2026 16:36
@dependabot @github

dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #37.

@dependabot dependabot Bot closed this Nov 16, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/morojs/engine-1.1.17 branch November 16, 2026 03:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants