New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix capturing group for matchAll #10136
fix capturing group for matchAll #10136
Conversation
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/11199/ |
In node 12 it is supported: you can use |
@nicolo-ribaudo apparently we dont have node 12 for the test env, https://github.com/babel/babel/blob/master/.travis.yml#L8 . somehow, it's supposed to be added here 80a5a2e, but the node env for travis is node 11, not node 12 |
We can add node 12 to the Travis yaml |
@tanhauhau we test node 12 via circle: https://github.com/babel/babel/blob/master/.circleci/config.yml#L37 |
@nicolo-ribaudo how do i add |
Doesn't adding it to the dev dependencies and then |
Hi, thanks so much for taking care of my reported issue. Is there anything I can do to help with moving it forward? |
cef8fb4
to
c727a1c
Compare
@mrtnzlml thanks for nudging, @nicolo-ribaudo i've added another fixture that test with core-js@v3 String.matchAll polyfill |
@@ -14,6 +14,7 @@ | |||
"repository": "https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-named-capturing-groups-regex", | |||
"bugs": "https://github.com/babel/babel/issues", | |||
"dependencies": { | |||
"core-js-pure": "^3.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be a devDependency
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops.. updated @existentialism
c727a1c
to
1dacdd5
Compare
I tried to use GitHub's "delete file" feature, thinking that it would have reverted the changes to a single file. I messed it up 😅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart for that, this PR looks good
Hi @nicolo-ribaudo, me again... 😊 Would you please consider merging this PR into master? |
@mrtnzlml We have a two-:heavy_check_mark:s policy for merging PRs; I'll try to find some reviewers! |
I was just waiting on the revert of the package.json to +1 |
857c9d2
to
e4f9369
Compare
Sorry my bad. fixed the wrong changes and reverts on |
e4f9369
to
2677f95
Compare
According to spec (https://github.com/tc39/proposal-string-matchall/blob/master/spec.md#stringprototypematchall--regexp-), when calling
String.matchAll
, the regex is recreated again with 'g' flag, and the currentBabelRegExp
constructor will take the 'g' flag as group descriptor.I see there's no
String.prototype.matchAll
support in node.js, not sure how to test this