Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

fix(deps): update dependency xregexp to v5 #76

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 9, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
xregexp (source) ^4.0.0 -> ^5.0.0 age adoption passing confidence

Release Notes

slevithan/xregexp

v5.1.1

Compare Source

v5.1.0

Compare Source

Breaking Changes

  • XRegExp.matchRecursive: When doing a global, non-sticky search and providing valueNames, return an empty array if no matches are found, rather than an array with one object containing a between value that contains the whole target string (this change is to match every other case when no matches are found, e.g. when not providing valueNames, not using global with flag g, or doing a sticky search with flag y): 6e1711e

Improvements

  • XRegExp.matchRecursive: Add support for matching with unbalanced delimiters (new unbalanced option with supported values 'error' [default], 'skip', and 'skip-lazy'): #​96
  • Upgrade to Unicode 14.0.0: 0f52a62

v5.0.2

Compare Source

  • Fix TypeScript definition for XRegExp.matchChain: #​325
  • Fix XRegExp.escape to handle -, ,, and # in a way that is compatible with ES6 flag u: #​323

v5.0.1

Compare Source

  • Hotfix for broken npm package.
  • Adds docs folder with extensive documentation.

v5.0.0

Compare Source

Breaking Changes

Improvements

Bug Fixes

v4.4.1

Compare Source

v4.4.0

Compare Source

  • Upgrade to Unicode 13.0.0
  • Add TypeScript definitions and tests #​285 #​286 #​288
  • Fix infinite loop in IE11 when used with core-js 3.6.0+ #​300

v4.3.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@slevithan
Copy link

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 restore the old handling so you don't need to update old code, run the following line after importing XRegExp: XRegExp.uninstall('namespacing').

XRegExp 4.1.0 and later allow introducing the new behavior without upgrading to XRegExp 5 by running XRegExp.install('namespacing').

Following is the most commonly needed change to update code for the new behavior:

// Change this
const name = XRegExp.exec(str, regexWithNamedCapture).name;

// To this
const name = XRegExp.exec(str, regexWithNamedCapture).groups.name;

Let me know if you have any questions and I'll be happy to help!

@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants