Meta: Upgrade ESMeta to v0.6.4 #3656
Merged
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
bakkot
approved these changes
Jul 18, 2025
michaelficarra
approved these changes
Jul 18, 2025
michaelficarra
added
the
ready to merge
jhnaldo
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
I directly updated v0.6.4 instead of v0.6.3.
It resolves the CI failure that appears in #3653 by fixing bugs related to handling the
function objectandconstructortypes by revising the intersection and normalization of record types (es-meta/esmeta#300).It supports more detailed reporting with the number of occurrences of each unique phrase (es-meta/esmeta#287).
It adds type modeling for each separate case of
TypedArray(e.g.Uint8Array) to resolve the type check error in #3655 (es-meta/esmeta#304)