Bump version to 5.0.0

[josephfrazier]

Changes include:

• BREAKING: Handle ES2018 capture names: BREAKING: Handle ES2018 capture names #247
• BREAKING: Enable namespacing feature by default: BREAKING: Enable namespacing feature by default #316
• BREAKING: Remove Unicode Blocks addon: 4860122
• restore perf tweak that made a meaningful difference in regex construction perf tests: 5f18261
• XRegExp.exec: preserve groups obj that comes from native ES2018 named capture: c4a83e7
• Make XRegExp.exec set groups prop to undefined if there are no named captures (closes groups property of matchObj for regex without named capture should have value undefined #320): 7fea476
• Support optional 'Script=' prefix (from ES2018 syntax) for Unicode script tokens (Align with native Unicode property escapes #225): bb35ead
• XRegExp.matchRecursive: Add delimiter and pos info when unbalanced delimiters are found (closes Can we have some position information in Unbalanced delimiter error? #293): 9660b90
• XRegExp.escape: Escape whitespace in a way that works with ES6 flag u (fixes Escape function returns regex that is incompatible with 'u' flag #197): e22a52b

To generate this commit, I adapted the steps at #205 (comment)

Here's a fuller list of changes that can be needed with new releases:

• Version number
  • Update version number and year in headers, config files, README.
  • Update version number in XRegExp.version.
• Publish
  • Publish new git tag. E.g.:
    • git tag -a v3.1.0 -m "Release 3.1.0".
    • git push origin v3.1.0.
  • npm publish.

[slevithan]

Sweet!

I've just finished a major update for every page on xregexp.com, updating the docs for v5.0.0. The last time it was updated was for v3.2.0 so it was fairly out of date! E.g., it didn't yet include XRegExp.tag.

To make the documentation easier to keep up to date, I've added all the content from xregexp.com to the repo here in the new docs folder. (This was requested years ago.) It contains locally browse-able webpages.

Note that after you published, I fixed the version number in README, removing "-next" (124adc0). Sorry about the confusion... I'd changed the version there to say 4.4.1-next since I'd previously updated README to reflect v5 API changes (so putting a v4.4.1 heading on it was misleading). I didn't want it to say 5.0.0 though until v5 was ready to go -- hence 4.4.1-next.

[slevithan]

Thanks again for releasing this! I've updated the release notes at https://github.com/slevithan/xregexp/releases/tag/v5.0.0 to more fully cover the changes in v5.0.0 (added a few things and removed "restore perf tweak" since that wasn't a change relative to v4.4.1):

Breaking Changes

• Enable the namespacing feature by default for alignment with ES2018 (moves named capture properties to the groups object of matches and to the last argument of replacement callbacks): BREAKING: Enable namespacing feature by default #316
• Handle ES2018 capture names (mostly this adds support for an extended set of Unicode characters, but it also prevents using a number as the first character in a capture name): BREAKING: Handle ES2018 capture names #247
• Remove support for Unicode blocks, for alignment with ES2018 (use Unicode scripts instead): Align with native Unicode property escapes #225

Improvements

• Support optional 'Script=' prefix (from ES2018 syntax) for Unicode script tokens: Align with native Unicode property escapes #225
• XRegExp.matchRecursive: Add delimiter and position info to error when unbalanced delimiters are found: Can we have some position information in Unbalanced delimiter error? #293
• Avoid inserting unneeded (?:) into native regex source in more cases: 076f950 and d78a262
• Defer to native flag s in ES2018 environments: 98abea8

Bug Fixes

• XRegExp.exec: Preserve the groups object that comes from native ES2018 named capture: c4a83e7
• XRegExp.exec: Set the groups property to undefined if there are no named captures: groups property of matchObj for regex without named capture should have value undefined #320
• XRegExp.escape: Escape whitespace in a way that works with ES6 flag u: Escape function returns regex that is incompatible with 'u' flag #197
• XRegExp.replace: Throw when using native named capture and a numbered backreference one higher than the number of captures in the same regex: Should throw when using XRegExp.replace with native named capture and numbered backref one higher than number of captures #317
• XRegExp.replace: Fix edge case issues with replacement text syntax: Fix edge case issues with replacement text syntax #318