Steven Levithan

Yeah, my Regex+ and Oniguruma-To-ES libraries, which [both](https://github.com/slevithan/regex/blob/main/package.json) [include](https://github.com/slevithan/oniguruma-to-es/blob/main/package.json) dual ESM and CJS bundles, use separate `require` and `import` properties in their `exports`. But it's not that simple. In order...

Cool to see you got the CJS package working. I've linked to it in the readme. > I guess you could do this as well > decrease package size a...

Any fixes upstream will automatically be updated here. > I can submit a PR with the fix if you'd like. Submitting a PR upstream would probably help it get fixed...

Thanks for the thoughtful response, @firasdib. Those are very reasonable concerns, and of course no hard feelings if you feel that it's not the right fit. Some thoughts in response:...

Awesome--I'll be happy to help however I can. Note: Since regex101 would need to call `regex` with dynamic input rather than using it with backticks as a template tag, that...

Heads up that `regex` [4.0.0](https://github.com/slevithan/regex/releases) was just released, and it includes a few things that would be relevant for regex101. - The new `subclass: true` option should always be used...

Just a note that regex 4.1 added support for [possessive quantifiers](https://github.com/slevithan/regex#possessive-quantifiers). That completes all syntax I've wanted to add (and what I consider to be the most important features missing...

To help with challenges around referring to the library/flavor (which I agree was a significant issue), I've now adopted the official name Regex+. It could now be listed as e.g....

> This can be fixed by changing the final group from being a capture group to a lookahead. > > Current final group: `(?:\s|;|$)` > > As a lookahead: `(?=:\s|;|$)`...

If you are open to the breaking change proposed above, I see at least three paths: 1. Simply no longer provide this functionality. Although this feels like a loss, it...