Update dependency Jint to 4.16.1 - #1192
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.16.0→4.16.1Release Notes
sebastienros/jint (Jint)
v4.16.1: 4.16.1Jint 4.16.1 is the first release from the new
4.xmaintenance branch, and it marks the point where the two lines separate:mainis now 5.0.0 development, and4.xis where the 4.16.x line continues.What that means for you. If you are on 4.16.0, this is a drop-in update — it is correctness and conformance work only, no API change and no changed default. Every public signature is the same one 4.16.0 shipped, on all five target frameworks. If you want the 4.x line, take it from
4.xand expect fixes rather than features. If you want to follow where the engine is going, watchmain— v5 brings breaking API changes, an opt-in WHATWG web API surface, Web Workers, Node compatibility and a raised .NET Framework floor, and every one of them is recorded as it lands indocs/v5-migration.md.From this release onward the 4.x public surface is snapshotted per target framework in
Jint.Tests.PublicInterface/Verify/, so "did the API move?" is a diff rather than a judgement call — on this branch a diff there is a bug, and comparing those files againstmain's is the v4→v5 delta.Highlights
Conformance, from a suite that now runs more of test262. The
staging/directory is generated and executed for the first time (#3016), which is roughly 2,800 additional cases — largely SpiderMonkey's own suite contributed upstream, covering behaviour the stable directories never reach. Much of the work below is what it found.Built-ins do what the spec says, step by step. The array built-ins perform the internal methods they name rather than equivalents (#3066);
Array.fromhonoursIsConstructorand a typed array'slengthwrite throws (#3043); an array truncation walks downwards and the generics report the writes they fail (#3072); argument validation and evaluation order are corrected in five built-ins (#3069);MapandSetget the[[SetData]]tombstone their traversals are specified over (#3073);Date.prototype.setTimestores the clipped time value (#3042); andArray.prototype.values/keys/entriesno longer gate on an array-like receiver (#3236).Iterators and control flow. A throw from the iterator step no longer closes the iterator (#3047); the
doneflag is consulted before stepping again (#3048); a rejectedreturn()propagates out of an abandonedfor awaitloop (#3113); an optional-chain short circuit is distinguished from a genuineundefined(#3040); a computed property key is evaluated even when spelled as a literal (#3039) and survives anawaitoryieldintact (#3144, #3150); and destructuring the rest of an exhausted array yields an empty array rather than 2³² elements (#3263).Numeric and string accuracy.
Math.acosh,asinh,atanh,cbrt,expm1andlog1pare ported from fdlibm for correctly-rounded results across every target framework (#3050);toFixedformats from the double's exact value and readsthisfrom[[NumberData]](#3071);String.prototypecase conversion derives from Jint's own Unicode tables rather than the host's culture data (#3068); and the regex engine is chosen per subject, withRegExp.prototype.replaceno longer rewritinglastIndex(#3070).Bounds that hold. JavaScript strings have a maximum length instead of a wrapped array rent (#3015); a JSON document too long to become a string is refused while it is being built (#3028); a frame displaced by a proper tail call keeps counting while its trampoline runs, so
MaxRecursionDepthcannot be evaded by leaving and re-entering the trampoline (#3022); and anAtomicswaiter is released when nothing can ever notify it again (#3029).Error messages no longer run user JavaScript (#3041) — rendering a message for a value with a script-supplied
toStringused to invoke it, from inside the failure path.Internationalization. The five Temporal members the proposal removed are dropped (#3014), and
u-extension options are canonicalized with every date format the spec allows (#3018).Two fixes in this release come from @svenrog — a sloppy function answering its own
arguments(#3061) and the outer link on a parkedFunction-constructor environment (#3063).What's Changed
Full Changelog: sebastienros/jint@v4.16.0...v4.16.1
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.