babel-preset-stage-2: Add transform-unicode-property-regex #3683

Open
wants to merge 1 commit into
from

Projects

None yet

2 participants

@mathiasbynens
Contributor
mathiasbynens commented Aug 29, 2016 edited

Note: This transform depends on regexpu-core which supports Node.js v4+ only. So, this patch is blocked by https://phabricator.babeljs.io/T7392 / #4315.


This enables the use of Unicode property escapes of the form \p{…} and \P{…} in regular expressions with the u flag enabled.

@mathiasbynens mathiasbynens referenced this pull request in babel/babel.github.io Aug 29, 2016
Open

Add transform-unicode-property-regex docs #904

@hzoo hzoo added this to the Next Major milestone Aug 31, 2016
@hzoo
Member
hzoo commented Jan 14, 2017

@mathiasbynens can you rebase again? looks like we changed the presets to be "es modules".

Should we just move the plugin into the repo (don't have to)?

@mathiasbynens mathiasbynens babel-preset-stage-2: Add transform-unicode-property-regex
This enables the use of Unicode property escapes of the form `\p{…}` and `\P{…}` in regular expressions with the `u` flag enabled.

More info: https://mathiasbynens.be/notes/es-unicode-property-escapes
Proposal: https://github.com/mathiasbynens/es-regexp-unicode-property-escapes
Plugin: https://github.com/mathiasbynens/babel-plugin-transform-unicode-property-regex
37a5fb2
@mathiasbynens mathiasbynens changed the title from babel-preset-stage-1: Add transform-unicode-property-regex to babel-preset-stage-2: Add transform-unicode-property-regex Jan 14, 2017
@mathiasbynens
Contributor

Rebased.

Should we just move the plugin into the repo (don't have to)?

I’d prefer to keep it under my own account for now, so I can more easily keep it in sync with the proposal.

@hzoo
Member
hzoo commented Jan 14, 2017 edited

Cool all good with me. We are going to use "independent" mode in lerna going forward in Babel 7 which just means we can publish all modules individually so we can at least update all stage-x presets and proposal plugins when necessary (only reasonable).

Also we'll want to move these prs to point to the new 7.0 branch (we can do this too in the github interface)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment