Change the parser to allow the RegExp d flag.

[ota-meshi]

💻

• Would you like to work on this feature?

What problem are you trying to solve?

RegExp literals can now use the d flag, but the d flag causes a parsing error.

https://github.com/tc39/proposals/blob/master/finished-proposals.md
tc39/proposals@f0adbe1
https://github.com/tc39/proposal-regexp-match-indices
tc39/ecma262#1713

Describe the solution you'd like

Change the parser so that the d flag of the RegExp literal does not cause a parsing error.

I'm not familiar with it, but I might just add the flag to the next line.
https://github.com/babel/babel/blob/main/packages/babel-parser/src/tokenizer/index.js#L24

Describe alternatives you've considered

I don't think there is an alternative.

Documentation, Adoption, Migration Strategy

No response

[babel-bot]

Hey @ota-meshi! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite."

[nicolo-ribaudo]

Thanks for the bug report! This needs to be fixed adding the flag to

babel/packages/babel-parser/src/tokenizer/index.js

Line 24 in 813f2a3

const VALID_REGEX_FLAGS = new Set(["g", "m", "s", "i", "y", "u"]);

Then, we should add a test in https://github.com/babel/babel/tree/main/packages/babel-parser/test/fixtures/es2022.

[nicolo-ribaudo]

I'm assigning this issue to you since you ticked "Would you like to work on this feature?" 😄
If you need any help, feel free to ask!