如何找出哪些JavaScript引擎/平台支持ES6 Unicode正则表达式的哪些功能?[英] How can I find out which JavaScript engines/platforms support which features of ES6 Unicode regular expressions?

本文是小编为大家收集整理的关于如何找出哪些JavaScript引擎/平台支持ES6 Unicode正则表达式的哪些功能?的处理/解决方法,可以参考本文帮助大家快速定位并解决问题,中文翻译不准确的可切换到English标签页查看源文。

问题描述

我经常使用许多人类语言和写作系统,并且尝试使用我可以使用的JavaScript的最现代功能.

我经常发现我想使用现代的Unicode正则表达式,例如Unicode属性逃逸:

/\p{L}/

看来,尽管许多JS平台都包含越来越多的ES6功能,但这些Unicode Regex功能仍在落后.

我如何找到哪些引擎/平台支持这些功能中的哪一个?通过"平台",我包括诸如transpilers之类的东西.

我知道出色的 xregexp 进行出色的解决方法,但是我如何监视/跟踪此支持在各种JS实现中被本地包含在内?

我想像我可以使用可能是我想要的.但是,也许跟踪ES6支持,跟踪Unicode支持或跟踪正则表达式支持的东西也可能存在?也许我可以订阅各种错误报告和功能请求?

推荐答案

compat-topat-norefortable "> compat-topate regexp_unicode_property_properperperperperpety /p>

一些相关功能

  • u_flag
  • u_flag
  • s_flag href =" https://mathiasbynens.be/notes/es-regexp-proposals#dotall" rel =" nofollow noreferrer"> us combo combo ex
  • )

其他推荐答案

代替了完整的集中资源,这是我至少可以以正则表达式的Unicode属性逃逸到目前为止所能定位的问题/功能跟踪器:

本文地址:https://www.itbaoku.cn/post/1095214.html

问题描述

I often work with many human languages and writing systems and I try to use the most modern features of JavaScript that I can.

I often find I would like to use modern Unicode regular expression such as Unicode Property Escapes:

/\p{L}/

It seems that though many JS platforms are including more and more ES6 features, these Unicode regex features are lagging behind.

How can I found out which engines/platforms support which of these features? By "platform" I include things like transpilers.

I'm aware of the excellent XRegExp for a great workaround, but how can I monitor/track this support getting included natively in the various JS implementations?

I suppose something like Can I use might be what I'm looking for. But maybe something that tracks ES6 support, that tracks Unicode support, or that tracks regular expression support might also exist? Or maybe there are various bug reports and feature requests I can subscribe to?

推荐答案

compat-table for RegExp_Unicode_Property_Escapes feature

Some related features

其他推荐答案

In lieu of a full centralized resource, here's the issue/feature trackers I've been able to locate so far at least for Unicode property escapes in regular expressions: