fix: reset global regex before match #11132
Merged
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.
Description
I noticed we're not properly resetting the global regex when running while-loop regex match, which means the result we could be missing regex captures every other run. (StackOverflow explanation)
Additional context
I'm not sure how we haven't got a bug report for this before 😬
MDN has notes about how
lastIndexis set. I also find that using global regex forstr.replaceorstr.matchare not affected by.lastIndex, and it would also always reset.lastIndex. (Maybe that's how the bug appear less often for some regex)What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123).