fix(utils): clone RegExp values with new RegExp instead of structuredClone (fix #19245, fix #18875)
#19247
Conversation
This file contains 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
7 tasks
…turedClone` (fix #19245, fix #18875) - Jest appears to provide its own global `structuredClone` that modifies `RegExp`s in such a way that they fail `instanceof RegExp` checks, causing an error in a rollup plugin used by `vite` (and likely elsewhere). `new RegExp` seems to correctly clone `RegExp`s in Jest.
askoufis
force-pushed
the
fix/deep-clone-regexp
branch
from
313966b to
672e2ea
Compare
askoufis
changed the title
RegExp values with new RegExp instead of structuredClone (fix #19245, fix #18875)RegExp values with new RegExp instead of structuredClone (fix #19245, fix #18875)
patak-dev
approved these changes
Jan 21, 2025
sapphi-red
added
the
p2-edge-case
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.
Fixes #19245. Fixes #18875.
Description
Jest appears to provide its own global
structuredClonethat modifiesRegExps in such a way that they failinstanceof RegExpchecks, causing an error in a rollup plugin used byvite(and likely other errors elsewhere). As suggested,new RegExpseems to correctly cloneRegExps in Jest.I thought about writing a test that modified the
structuredCloneglobal but decided against it as that's more like testing jest implementation detail rather than regexp cloning behaviour (which is already tested).