Blake Embrey

> Would it be better if we exported the default regex from nocase and extend the array in this package? Yeah, that makes sense to me. Since it's a pretty...

Nice catch, thanks! I can make a new major release with unicode support and make a note of this in the README for browser support.

By the way, you probably want to look at https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions#Browser_compatibility instead. It shows that `\p` (Unicode property escapes) has always had much worse support and only recently got added to...

Feel free to leave it open until I release a new version 😄 Or submit a PR with the changes!

Let's change the defaults! It used to be that way using `XRegExp` but that increased the bundle size unreasonably, so using the native solution for the next major version seems...

I think this makes sense, it is interesting because it's possible that basing everything on a `no-case` standard to switch between has caused issues like this. I'll look into separating...

@adam-h I was able to achieve it in the current version using the built-in options, though it's not elegant (and V8 only due to look behinds): ```js { stripRegexp: /(?

Maybe we can re-use `Header-Case` and swap out the delimiter? However, that doesn't help much in the VS code extension. Is there a name for this format that's better than...

@aesptux Not really sure, I don't know a lot about testing under Python. I'd love if someone can jump in and give this a shot.

Been trying to think about this, not sure what the best way is. Was thinking maybe main headings for the sort of problems and also adding tags since they can...