## The problem

getAllValuesAsync throws an "invalid regular expression" SyntaxError when an "email contains" targeting rule has a value containing a + sign, for example [EMAIL]. The + was being interpolated into the generated regex without escaping, breaking evaluation for every function that runs the value evaluator.

## The fix

This was a ConfigCat SDK bug in how targeting-rule values were escaped when building the comparison regex. The team confirmed the root cause and shipped a patched SDK version shortly after the report. Upgrade the configcat-js (or your platform SDK) to a release newer than February 2022 and targeting rules with + in the value evaluate correctly.