Mathias Bynens

Let’s avoid the boolean trap, though: the second (optional) parameter should either be a string with flags or an object with settings (one of which could be `flags`, another could...

That last proposal sounds reasonable to me. We should be careful about adding sugar unless there is a strong need for it, though (generally speaking).

I haven’t looked at the code, but this _sounds_ like it could be a scoping issue.

Low-priority, since we have redirects in place.

Just make sure not to include a gzipped version. - `semicolon.js`: 1 byte - `semicolon.js.gz`: 34 bytes Please consider adding a note to the README, encouraging semicolon.js users not to...

Do we want to discuss this at the upcoming meeting, as a follow-up to the earlier discussion? If so, we should schedule it on day 1.

Given the complexity and large amounts of Unicode data involved, would it make sense to re-use [the regexpu-core implementation](https://github.com/mathiasbynens/regexpu-core) for this? I keep it up to date whenever Unicode updates,...

I think it makes sense to have this transpiler be a separate regexp-tree plugin, in a separate repo + npm package (regardless of your decision to re-use regexpu-core or to...

The living spec is here: https://w3c.github.io/webappsec/specs/upgrade/ ([Don’t link to TR copies](https://bugzilla.mozilla.org/show_bug.cgi?id=713433#c3))

AFAICT, remaining TODOs for this patch are: - [x] Follow the restructuring in #2716 and apply it to this patch. - [x] Rebase. (This is gonna be painful...) - [x]...