Skip to content

Update dependency Jint to 4.18.0 - #1192

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/jint-4.x
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/jint-4.x

Conversation

@renovate

@renovate renovate Bot commented Aug 23, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
Jint 4.16.0 → 4.18.0 age confidence

Release Notes

sebastienros/jint (Jint)

v4.18.0

Jint 4.18.0 is a release from the 4.x branch. It backports correctness and conformance fixes from main: 44 pull requests since 4.17.0, with no new public API. It is a minor release rather than a patch because it moves the parser to Acornima 1.9.1, and because limits a host has configured, MaxArraySize and RegexTimeout, now hold in places they did not. A script that relied on getting past them can now stop with an error. What might change for you below lists those cases and the two other changes a script can observe.

Highlights

A continue inside a labelled while or do-while no longer skips the code after the loop. In a: while (...) { ... continue; ... break a; }, an unlabelled continue was compared with the loop's label even though it had none. It left the loop as a completion nothing consumed: a function returned undefined instead of reaching its return, and a script skipped every statement after the loop. TypeScript's typescript.js scanner has exactly this shape, and under 4.17.0 it silently ignored /// <reference lib> directives (#​4563, from #​4557; regression tests #​4570; issue #​4568, reported by @​gentledepp). A continue naming any label stacked on a loop now continues it too.

Limits a host configured hold in more places.

  • Options.Constraints.MaxArraySize now bounds argument lists that a spread, apply, Reflect.apply/construct, a chain of bound functions or an ownKeys trap builds (#​4549, from #​4519), and new Array(n)'s fast path (#​4509). An engine with no MaxArraySize set pays one byte test.
  • RegexTimeout now bounds every regular expression built at run time (new RegExp(...), 'x'.match('...'), the splitter @@split builds), which ran under the parser package's 5 s default instead (#​4465, from #​3443). A regex in a Prepared<Script> now runs under the executing engine's RegexTimeout, rather than the 10 s default baked in when the script was prepared (#​4517, from #​3501).
  • An ArrayBuffer length the CLR cannot allocate raises a RangeError, and a maxByteLength it cannot allocate is rejected when the buffer is built (#​4463, #​4468).
  • A constraint that trips inside an iterator's return() during a throw close now propagates instead of being swallowed (#​4550, from #​4547).

Generators, async functions and iteration.

  • yield* throws a failing async delegate's error at the yield*, and forgets a delegation that ended by a throw (#​4326, #​4514).
  • A declaration list resumes at the declarator that suspended (#​4330).
  • A for await step that settles to a non-object throws the TypeError (#​4511), and an async generator records where it suspended for one (#​4521).
  • An iterator is closed with the completion the specification gives it, where a throw from return() was swallowed (#​4555).
  • An array pattern's elision (#​4561) and Iterator.prototype.drop (#​4562) no longer read a value they skip.
  • Destructuring calls a Symbol.iterator a script gave a wrapped CLR collection (#​4575, from #​4456; issue #​4427).

Functions, closures and exceptions.

  • An arguments object that an arrow function or a direct eval captured keeps its values after the call returns (#​4565, from #​4548; issue #​4545).
  • An arrow whose whole body is a direct eval, as in log => eval('() => log'), keeps its parameters reachable from what the eval creates (#​4572, from #​4370; issue #​4366).
  • When a catch parameter's binding throws, the finally block now runs before the error propagates (#​4571, from #​4389 by @​ewerton336; issue #​4336).
  • A throw keeps the thrown value when reading its message throws (#​4252).

Built-ins.

  • Promises: Promise.all, allSettled and any settle with the specification's remaining-elements count (#​4512). Promise.any builds its AggregateError directly (#​4506).
  • Numbers and dates: Math.pow and Math.round give the specification's results for large integral values (#​4497). BigInt shifts and asIntN/asUintN do so for any count (#​4467). An IANA Link time-zone name resolves through the zone it points to when the system lacks it (#​4488).
  • Regular expressions: five fixes to the custom RegExp engine and its fast paths (#​4249, #​4251, #​4253, #​4266, #​4294).
  • Strings: String.prototype.split converts a RegExp separator that has no @@split (#​4578, from #​4553).
  • Intl: Intl.ListFormat iterates its argument as the specification says (#​4576, from #​4448; issue #​4438). Intl.DurationFormat uses the specification's display defaults (#​4577, from #​4434 by @​ewerton336).

Hosts and interop.

  • A wrapped CLR collection deletes a configurable property the script defined on it (#​4508, from #​4499).
  • A wrapped IReadOnlyDictionary<string, T> whose Keys is not a collection now enumerates (#​4560, from #​4551).
  • Overload resolution scores a candidate without throwing when an argument cannot convert (#​4349, from #​4348).
  • A string built with s += t that a host reads from several threads while the engine is idle can no longer show the text from before its last appends on ARM64 (#​4573, from #​4255; issue #​4171).
  • A thrown object that is not an Error, frozen ones included, no longer gets an own stack property, and an engine-raised error's stack can be replaced in strict code (#​4574, from #​4446 by @​michaelthyregod; issue #​4430). JavaScriptException's stack trace for the host is unchanged.

Parser. Acornima 1.7.0 → 1.9.1 (#​4321, #​4464).

What might change for you
  • Configured limits fire where they did not before. With MaxArraySize set, an argument list or new Array(n) past it now throws; an engine that does not set it is unaffected. A regex built at run time now times out at RegexTimeout (10 s unless you set it) instead of at the parser package's 5 s, and a regex in a prepared script at the executing engine's RegexTimeout instead of 10 s.
  • e.stack on a thrown non-Error object is now whatever the object itself has (usually undefined), as in V8, instead of a string Jint added.
  • Intl.DurationFormat shows some zero units the specification says to show: new Intl.DurationFormat('en', { style: 'digital' }).format({ seconds: 1 }) is "0:00:01", not "00:01". A numeric sub-second unit with its display set to "always" is now a RangeError.
Verification

Every backport was verified failing-first: its tests ran against the unfixed 4.x tree on .NET 10 and .NET Framework 4.7.2, then again with the change. The release candidate was measured against 4.17.0 on all 50 SunSpider and Dromaeo rows in three paired rounds, alternating which build ran first in each round. The median row moved +0.25%, and per-row allocation moved by at most 1.4% (string-validate-input, which allocates less), and by under 0.2% on almost every row. Five rows read more than 1% slower in all three pairs. They were measured again in six more paired rounds, beside other engines' rows from the same benchmark class, whose packages are identical in both builds and so serve as a same-binary control. That control drifted by +1.2% to +6.8% per round against the candidate, so the machine's noise in that window was larger than the 1% this gate looks for. Corrected for it, no row regressed: every row's 95% interval includes zero.

What's Changed

Full Changelog: sebastienros/jint@v4.17.0...v4.18.0

v4.17.0

Jint 4.17.0 is a release from the 4.x branch. It backports correctness and conformance fixes from main (four of them for scripts that could end the host process), linear string building, and two new opt-in APIs for hosts. That is why it is a minor release rather than a patch. Nothing in it changes an existing API or an existing default, so it is a drop-in update from 4.16.4.

Highlights

A pooled engine can let go of a finished request's objects. Hosts that reuse one engine across many evaluations (CaptureGlobalSnapshot once, RestoreGlobalSnapshot between runs) keep the interpreter's warmed caches, and that is the point of reusing it. But a warmed call site remembers the last function it called, and a warmed member read remembers the last object it read from. In a pooled web host, that can be a delegate built from a finished request's services, which then stay alive until the same script runs again. The new Engine.Advanced.DiscardInterpreterCaches() drops those caches, so the objects can be collected. The engine, its intrinsics and its global object stay as they are. The next run of each script rebuilds its cache, which costs roughly what a first run on a new engine costs, minus building the engine. A good place to call it is when an engine has been idle for a while, rather than after every use (#​4229, from #​4227).

A host can carry its own state across await. Jint now runs ECMAScript's HostMakeJobCallback and HostCallJobCallback steps for every promise reaction, every thenable job and the FinalizationRegistry cleanup callback. A host can take part through the new Options.Host.JobCallbacks, which accepts a JobCallbackHooks with Capture, Enter and Exit callbacks. That lets each branch of a Promise.all fan-out keep its own host context, such as a logging scope or ambient request data, through every await (#​4231, from #​4230; issue #​4200). The default is no hooks, in which case each promise registration costs one null check and nothing a script can observe changes.

Four more ways for a script to end the host process are closed.

  • ShadowRealm. A failure crossing a ShadowRealm boundary threw its TypeError copy from inside the catch that was handling the original failure. That added a nested exception dispatch at every hop, and no stack check could see it. Even with the stack-overflow guard on, a long chain of wrapped functions ended the process on the way back out, and a three-line script with a name getter needed no chain at all. Building that copy also ran script (toString, getters, proxy traps); it no longer does. A failed importValue now reports the import failure instead of an unrelated error (#​4220, from #​4176 and #​4183).
  • instanceof and eval. instanceof now checks the native stack before calling a custom Symbol.hasInstance method, and eval checks it before parsing. A self-referencing Symbol.hasInstance, or var s = 'eval(s)'; eval(s), now raises a RangeError the script can catch instead of ending the process. On the MaxExecutionStackCount path, eval also stopped hopping to a new thread at each overflow without ever throwing. instanceof over a bound function now consults every bound link's own Symbol.hasInstance, as the specification requires (#​4221, from #​4172, #​4184 and #​4187).
  • These checks follow 4.x's existing rule. Like every other stack check on 4.x, they are active only when Options.Constraints.StackOverflowGuard is on, so turn it on for any script you do not fully trust.

Building a string with s = s + x is linear. A + whose result reaches 512 characters now produces a deferred string instead of copying both sides. Building with s = s + x, s = x + s and s = s + a + b therefore becomes linear, as s += x already was. Short concatenations take a separate path and pay nothing for this. The deferred string is safe to read from several engines that share one Prepared<Script>, and it is charged to LimitMemory when it is built, so a memory limit still bounds it. Binding an already-bound function also no longer copies its whole "bound …" name at every level (#​4160, from #​3386, #​3571, #​4130, #​4164 and #​4173).

Array.prototype.concat spreads host arrays and lists. Since 4.14, CLR arrays and lists reach script as live views by default. concat added such a view as a single element instead of spreading its items, so a.concat(b) returned the two wrappers. It now spreads anything script sees as an array (#​4219, from #​4216; issue #​4201).

TypedArray.prototype.with survives a shrinking coercion. When converting the index or the value made a resizable buffer shorter, with copied past its new end and let a CLR ArgumentException escape. It now copies only what the buffer still holds (#​4218, from #​4157).

Verification

Every backport was verified failing-first: its tests were run against the unfixed 4.x tree on .NET 10 and .NET Framework 4.7.2, then with the change. The release candidate was measured against 4.16.4 on SunSpider and Dromaeo in six paired rounds, alternating which build ran first in each round. The four Dromaeo ObjectRegExp rows ran 12–15% faster and SunSpider's 3d-raytrace 2.3% faster. No row regressed by 1% or more; the two rows whose interval did not include zero (one Dromaeo Cube variant, +0.70%, and SunSpider's controlflow-recursive, +0.88%) are within this machine's run-to-run noise.

What's Changed

Full Changelog: sebastienros/jint@v4.16.4...v4.17.0

v4.16.4

Jint 4.16.4 is a maintenance release from the 4.x branch. It backports correctness and conformance fixes from main — three of them for scripts that could end the host process — together with a few measured performance improvements, and nothing in it changes an existing API or an existing default. If you are on 4.16.3 it is a drop-in update — every public signature is the one 4.16.0 shipped, on all five target frameworks, and the per-framework snapshots in Jint.Tests.PublicInterface/Verify/ are unchanged. main remains 5.0.0 development; what is coming there is recorded as it lands in docs/v5-migration.md.

Highlights

A number reads as the same double on every target framework. Before .NET 9, the runtime's ulong-to-double and string-to-double conversions double-round, and Jint inherited that: a whole-number literal in [2⁶³, 2⁶⁴) held a different double on .NET Framework and .NET 8 than on .NET 10 (#​3531); parseFloat, Number and JSON.parse mis-rounded past their integer window on .NET Framework, and JSON.parse('1e999') threw a CLR OverflowException out of the engine instead of answering Infinity (#​3535); a fraction or exponent literal could land one ULP away on .NET Framework (#​3538); and parseInt and wide radix literals now hold the Number nearest the integer they denote on every framework, with a legacy octal no longer re-read as decimal (#​3537). The string-to-number lanes and trim now accept exactly the white space the parser does — U+0085 NEL no longer counts, and a byte-order mark no longer breaks Number or BigInt (#​3542) — and an exponent scan no longer clamps at 10⁶ (#​3593). All six arrive together as #​4120, because they share one parser. This changes numeric results — to the correct ones. The literal and string-to-number fixes change answers on .NET Framework only; parseInt, radix literals, the white-space set and the exponent clamp change them on every framework.

BigInt('+12') is 12n. The decimal spelling of a StringIntegerLiteral may carry a sign, so a leading + is accepted there and only there; BigInt('+0x10') stays a SyntaxError (#​4121).

A split keeps its segments when a constraint runs script. String.prototype.split filled a thread-shared scratch list and checks constraints every 10,000 segments; a host Constraint that ran script on the same thread could clear the list an outer split was still filling, which then returned only the segments added afterwards (#​4122).

An overload is not a fit for a number it cannot hold. Overload scoring gated float, short, byte and their kin on the value fitting, but not int and long — so 3000000000 was a perfect match for an int parameter, the wider overload beside it was never tried, and the host saw a CLR OverflowException rather than a catchable JavaScript error (#​4123).

Intl's locale lookup stops paying for a culture it does not need. BestAvailableLocale resolved a CultureInfo on every truncation step even though the available-locale set answers almost every lookup by itself; it now resolves one only when the set cannot answer (#​4124).

Intl.Locale canonicalizes every Unicode extension keyword value. UTS #​35 canonicalizes a keyword's value in two halves — the CLDR bcp47 aliases, and the removal of a value of "true" — and Jint did only the first, while Intl.Locale's own tag scanner did neither. So en-u-ca-true kept its true, en-u-kb-yes kept its yes although the data aliases it to true, and en-u-ks-primary was never aliased to level1 on the tag path. The firstDayOfWeek option was read as a Number before a String and cast to int, so 0.5 resolved to "sun" where the spec rejects it, and NaN and Infinity became whatever the framework's cast made of them — which differed between .NET and .NET Framework (#​4156).

An object used as a rotating cache stops compacting forever. A property removed from an object's store leaves a tombstone, so that a re-added key keeps its creation order. Removing the newest entry already reclaimed its slot; removing the oldest — the shape of a bounded cache, a fresh name in and the oldest out — left a hole each time, and the table compacted every capacity − live additions although the live set never grew: a 16-key rotation settled on a capacity of 64 and compacted 209 times per 10,000 steps. The entries are now a window that may wrap around the array, so a removal at either end retires its slot; the same rotation never resizes and settles on 32 (#​4155).

Chains that script can make as long as it likes no longer end the process. Resolving a property through a prototype chain recursed one native frame per link, so a 20,000-deep { __proto__: x } chain overflowed the native stack on a read, a write, an in or a with lookup and ended the process — nothing thrown, nothing for a catch to see (#​4170, from #​4078; issue #​4076, reported by @​Tielem). [[Get]], [[Set]] and [[HasProperty]] now walk the chain in a loop, so an ordinary or shaped-host-prototype chain of any depth simply answers. Function.prototype.bind chains had the same shape in IsConstructor and in the realm lookup new and Reflect.construct perform, and those are loops now too (#​4169, from #​4165); on .NET Framework the JIT happened to turn both into tail calls, so the process death was a .NET 8 / .NET 10 one.

Two chains cannot be flattened, because each link has work of its own to do on the way back out: a proxy forwarding to a proxy, and host object wrappers stacked on each other (#​4170, from #​4125; issue #​4087). Those are probed instead, and raise a catchable RangeError — when Options.Constraints.StackOverflowGuard is on. On 4.x that guard remains opt-in (it becomes the default only in 5.0), so an engine left at its defaults still ends the process on a deep enough proxy chain. If you run script you do not control, turn the guard on; with it on, a 20,000-link proxy chain used as an array's constructor or as Reflect.construct's newTarget now raises RangeError where it used to end the process.

% stops allocating for numbers. The remainder operator now takes the unboxed numeric lane multiplication and division already used, so sum += i % 97 reads a numeric counter without materialising a JsNumber per step — on the benchmark's arithmetic loop, allocation per run drops from 2.87 MB to under 1 KB (#​4167, from #​4154).

Intl.Locale.prototype.getWeekInfo reads the region the specification picks. It read CLDR's week data for the tag's literal region subtag only, so a tag without one got the world's week and the -u-rg- and -u-sd- keywords were ignored. It now follows RegionPreference: a -u-rg- override, then the region subtag, then a -u-sd- subdivision's region, then the region Add Likely Subtags supplies, then 001. This changes answers — new Intl.Locale('en').getWeekInfo().firstDay is now 7 (en is likely en-US, where the week starts on Sunday) rather than 1, and en-US-u-rg-gbzzzz answers 1 rather than 7 — in each case to what the specification and every browser give (#​4168, from #​4163).

Verification

Every backport was verified failing-first: its tests were run against the unfixed 4.x tree on .NET 10 and .NET Framework 4.7.2, then with the change.

PR tests unfixed .NET Framework unfixed .NET 10 after
#​4120 (#​3531) whole-number literals, 22 15 fail 0 fail all pass
#​4120 (#​3535) string to number, 41; JsonTests, 170 22 + 8 fail 0 fail all pass
#​4120 (#​3538) fraction / exponent literals, 50 16 fail 0 fail all pass
#​4120 (#​3537) parseInt, 124; radix literals, 21 96 + 12 fail 96 + 12 fail all pass
#​4120 (#​3542) white space, 35 22 fail 22 fail all pass
#​4120 (#​3593) exponent clamp, 5 1 fail 1 fail all pass

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner August 23, 2026 13:44
@renovate
renovate Bot force-pushed the renovate/jint-4.x branch 2 times, most recently from 09e2589 to 957ed55 Compare September 2, 2026 12:54
@renovate
renovate Bot force-pushed the renovate/jint-4.x branch 2 times, most recently from c0ef7dc to fb3e086 Compare September 9, 2026 19:57
@renovate renovate Bot changed the title Update dependency Jint to 4.16.1 Update dependency Jint to 4.16.2 Sep 9, 2026
@renovate
renovate Bot force-pushed the renovate/jint-4.x branch from fb3e086 to b218deb Compare September 19, 2026 12:19
@renovate renovate Bot changed the title Update dependency Jint to 4.16.2 Update dependency Jint to 4.16.3 Sep 19, 2026
@renovate
renovate Bot force-pushed the renovate/jint-4.x branch 2 times, most recently from 23b28f0 to 23c46a2 Compare September 25, 2026 10:44
@renovate renovate Bot changed the title Update dependency Jint to 4.16.3 Update dependency Jint to 4.16.4 Sep 25, 2026
@renovate
renovate Bot force-pushed the renovate/jint-4.x branch 2 times, most recently from 5939aff to c20c978 Compare October 7, 2026 05:57
@renovate renovate Bot changed the title Update dependency Jint to 4.16.4 Update dependency Jint to 4.17.0 Oct 7, 2026
@renovate
renovate Bot force-pushed the renovate/jint-4.x branch from c20c978 to 35141cf Compare October 27, 2026 00:14
@renovate
renovate Bot force-pushed the renovate/jint-4.x branch from 35141cf to 53acae7 Compare November 13, 2026 23:02
@renovate renovate Bot changed the title Update dependency Jint to 4.17.0 Update dependency Jint to 4.18.0 Nov 13, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants