Steven Levithan

Yes, this is possible now in ES2018 environments. But first you need to define what a Unicode word character is. I'll use the rough approximation `\p{L}\p{M}*`, which matches any Unicode...

That's a clever workaround, @josephfrazier. Extending on that, multiple custom tokens can check whether the same feature (e.g. Ruby regex syntax) is installed or not, so they can be installed/uninstalled...

Yeah, as @josephfrazier said, this is intentional and documented (though perhaps the documentation could be more explicit). `XRegExp` has two modes: it either takes a regex pattern string with optional...

@abozhilov described why this is used. You can't subclass builtins like `RegExp` prior to ES6 (ES 2015). In fact XRegExp already has an alternative/fallback for browsers that don't support `__proto__`....

This would also enable `(?(?...)(?...))` blocks that make subpattern reuse via `(?&name)` and `(?n)` more robust.

Thanks for the report, @jeriewang, and for offering to submit a PR to fix it! Would you mind opening a PR with the desired change?

Supporting `Script_Extensions` is the biggest change here. It might make sense to merely ensure that use of `Script_Extensions` (which is easy to identify since ES2018 requires a prefix when using...

Removed support for Unicode blocks in commit 4860122362c9822f35ab7f2deea7973a5815fcac.

Happy to hear your ideas about what specifically would be changed and how this would be achieved. And I'd be happy to consider PRs. Note that XRegExp is already split...

New diffs 076f9501965d9ddc4f1cf7b7626c77993b396a01 and d78a26216691c975acf5424f371db9763f307c7a cleaned up more cases where `(?:)` isn't needed. Specifically, the following are now covered: * Before a group (left of `(`). * After a group...