Steven Levithan

I don't think this should be treated as a breaking change, since `isBmpLast` is unlikely to be used by any existing addons outside of the official XRegExp Unicode addons (which...

A few things I noticed: - Many of the links would benefit from descriptions. - I don't understand why some of the links under "Official Docs" are included. Apart from...

Thanks for your list. Technical writing is a subject I'm curious to learn more about. Leaving aside the lint errors, there are a lot of minor issues with language. Numerous...

Hi! XRegExp v5 has a breaking change described at https://github.com/slevithan/xregexp#named-capture-breaking-change-in-xregexp-5 Specifically, named backreference properties now appear on the result's groups object (following ES2018), rather than directly on the result. To...

Named capturing syntax is now supported in v0.4.0.

@mgoldenbe the code works fine but you are incorrectly passing `"uA"` as a third argument to `XRegExp.exec` rather than as the second (`flags`) argument to the `XRegExp` constructor. However, I...

@mgoldenbe there are a couple potential advantages to using the XRegExp addon above over the solution in that post, especially if you're already including XRegExp in your code: 1. You...

Alternative library [Regex.make](https://github.com/slevithan/regex-make) takes a more exhaustive approach to this, and might be instructive. > ClassAtom as Range delimiters: `` RegExp.make`[${"a"}-${"z"}]` `` - is anything but a single-codepoint string valid...

I would have personally preferred `\G` over the `y` flag, but since we already have `y`, the use cases for `\G` are significantly reduced. Basically it only still makes sense...

> **Motivation:** > This is a useful feature that cannot be implemented using other regex features. The most common way it's used -- putting `\G` at the start of a...