This is a Ruby gem that translates Ruby's regular expressions to the JavaScript flavor.
It can handle far more of Ruby's regex capabilities than a search-and-replace approach, and if any incompatibilities remain, it returns helpful warnings to indicate them.
This means you'll have better chances of translating your regexes, and if there is still a problem, at least you'll know.
Add it to your gemfile or run
gem install js_regex
In Ruby:
require 'js_regex'
ruby_hex_regex = /0x\h+/i
js_regex = JsRegex.new(ruby_hex_regex)
js_regex.warnings # => []
js_regex.source # => '0x[0-9A-Fa-f]+'
js_regex.options # => 'i'An options: argument lets you force options:
JsRegex.new(/x/i, options: 'g').to_h
# => {source: 'x', options: 'gi'}Set the g flag like this if you want to use the regex to find or replace multiple matches per string.
To inject the result directly into JavaScript, use #to_s or String interpolation. E.g. in inline JavaScript in HAML or SLIM you can simply do:
var regExp = #{js_regex};Use #to_json if you want to send it as JSON or #to_h to include it as a data attribute of a DOM element.
render json: js_regex
js_regex.to_h # => {source: '[0-9A-Fa-f]+', options: ''}To turn the data attribute or parsed JSON back into a regex in JavaScript, use the new RegExp() constructor:
var regExp = new RegExp(jsonObj.source, jsonObj.options);You might have noticed the empty warnings array in the example above:
js_regex = JsRegex.new(ruby_hex_regex)
js_regex.warnings # => []If this array isn't empty, that means that your Ruby regex contained some stuff that can't be carried over to JavaScript. You can still use the result, but this is not recommended. Most likely it won't match the same strings as your Ruby regex.
advanced_ruby_regex = /(?<!fizz)buzz/
js_regex = JsRegex.new(advanced_ruby_regex)
js_regex.warnings # => ["Dropped unsupported negative lookbehind assertion '(?<!fizz)' at index 0"]
js_regex.source # => 'buzz'In addition to the conversions supported by the default approach, this gem will correctly handle the following features:
| Description | Example |
|---|---|
| escaped meta chars | \\A |
| dot matching astral chars | /./ =~ '😋' |
| Ruby's multiline mode [1] | /.+/m |
| Ruby's free-spacing mode | / http (s?) /x |
| atomic groups [2] | a(?>bc|b)c |
| conditionals [2] | (?(1)b), (?('a')b|c) |
| option groups/switches | (?i-m:..), (?x).. |
| local encoding options | (?u:\w) |
| absence groups | /\*(?~\*/)\*/ |
| possessive quantifiers [2] | ++, *+, ?+, {4,}+ |
| hex types \h and \H | \H\h{6} |
| bell and escape shortcuts | \a, \e |
| all literals, including \n | eval("/\n/") |
| newline-ready anchor \Z | last word\Z |
| generic linebreak \R | data.split(/\R/) |
| meta and control escapes | /\M-\C-X/ |
| numeric backreferences | \1, \k<1> |
| relative backreferences | \k<-1> |
| named backreferences | \k<foo> |
| numeric subexpression calls | \g<1> |
| relative subexpression calls | \g<-1> |
| named subexpression calls | \g<foo> |
| nested sets | [a-z[A-Z]] |
| types in sets | [a-z\h] |
| properties in sets | [a-z\p{sc}] |
| set intersections | [\w&&[^a]] |
| recursive set negation | [^a[^b]] |
| posix types | [[:alpha:]] |
| posix negations | [[:^alpha:]] |
| codepoint lists | \u{61 63 1F601} |
| unicode properties | \p{Arabic}, \p{Dash} |
| unicode abbreviations | \p{Mong}, \p{Sc} |
| unicode negations | \p{^L}, \P{L}, \P{^L} |
| astral plane properties [2] | \p{emoji} |
| astral plane literals [2] | 😁 |
| astral plane ranges [2] | [😁-😲] |
[1] Keep in mind that Ruby's multiline mode is more of a "dot-all mode" and totally different from JavaScript's multiline mode.
[2] See here for information about how this is achieved.
Currently, the following functionalities can't be carried over to JavaScript. If you try to convert a regex that uses these features, corresponding parts of the pattern will be dropped from the result.
In most of these cases that will lead to a warning, but changes that are not considered risky happen without warning. E.g. comments are removed silently because that won't lead to any operational differences between the Ruby and JavaScript regexes.
| Description | Example | Warning |
|---|---|---|
| lookbehind | (?<=, (?<!, \K | yes |
| whole pattern recursion | \g<0> | yes |
| backref by recursion level | \k<1+1> | yes |
| previous match anchor | \G | yes |
| extended grapheme type | \X | yes |
| variable length absence groups | (?~(a+|bar)) | yes |
| working word boundary anchors | \b, \B | yes [3] |
| capturing group names | (?<a>, (?'a' | no |
| comment groups | (?#comment) | no |
| inline comments (in x-mode) | /[a-z] # comment/x | no |
| multiplicative quantifiers | /A{4}{6}/ =~ 'A' * 24 | no |
[3] \b and \B are carried over, but generate a warning because they only recognize ASCII word chars in JavaScript. This holds true for all JavaScript versions and RegExp modes.
JsRegex uses the gem regexp_parser to parse a Ruby Regexp.
It traverses the AST returned by regexp_parser depth-first, and converts it to its own tree of equivalent JavaScript RegExp tokens, marking some nodes for treatment in a second pass.
The second pass then carries out all modifications that require knowledge of the complete tree.
After the second pass, JsRegex flat-maps the final tree into a new source string.
Many Regexp tokens work in JavaScript just as they do in Ruby, or allow for a straightforward replacement, but some conversions are a little more involved.
Atomic groups and possessive quantifiers are missing in JavaScript, so the only way to emulate their behavior is by substituting them with backreferenced lookahead groups.
Astral plane characters convert to ranges of surrogate pairs, so they don't require ES6.
Properties and posix classes expand to equivalent character sets, or surrogate pair alternations if necessary. The gem regexp_property_values helps by reading out their codepoints from Onigmo.
Character sets a.k.a. bracket expressions offer many more features in Ruby compared to JavaScript. To work around this, JsRegex calls on the gem character_set to calculate the matched codepoints of the whole set and build a completely new set string for all except the most simple cases.
Conditionals expand to equivalent expressions in the second pass, e.g. (<)?foo(?(1)>) expands to (?:<foo>|foo) (simplified example).
Subexpression calls are replaced with the conversion result of their target, e.g. (.{3})\g<1> expands to (.{3})(.{3}).
The tricky bit here is that these expressions may be nested, and that their expansions may increase the capturing group count. This means that any following backreferences need an update. E.g. (.{3})\g<1>(.)\2 (which matches strings like "FooBarXX") converts to (.{3})(.{3})(.)\3.
Feel free to send suggestions, point out issues, or submit pull requests.
Possible future improvements might include an "ES6 mode" using the u flag, which would allow for more concise representations of astral plane properties and sets.
As far as supported conversions are concerned, this gem is pretty much feature-complete. Most of the unsupported features listed above are either impossible or impractical to replicate in JavaScript.