If you're not familiar with
test method. If the string matches the regex, the method returns
true. Otherwise it returns
There's one caveat.
If the regex being tested contains the global flag,
regex.test(str) relies on more than just the input
So what's going on?
To put it in functional programming terms—
regex.test is not a pure function if you use the
g flag on your regex.
Here's an example of this behavior in action.
// note that we're using the `g` flag const regex = /test/g // returns true regex.test('test123') // returns false 😭 regex.test('test123') // returns true regex.test('test123')
Both methods set the
lastIndex value on the regex to the last matched index. But they only do this if the regex has the
g flag. If the end of the string is reached without finding any matches,
lastIndex is set to
Here's the same example from before, but also showing the value of
// note that we're using the `g` flag on the const regex = /test/g console.log(regex.lastIndex) // 0 // returns true regex.test('test123') console.log(regex.lastIndex) // 4 // returns false 😭 regex.test('test123') console.log(regex.lastIndex) // 0 // returns true regex.test('test123') console.log(regex.lastIndex) // 4
How do we work around this quirk?
Certainly the simplest way to get around this issue is to remember that
regex.test behaves like this if the
g flag exists and not use it on regexes that have the
Especially if the primary usage of the regex is testing strings, we probably don't need the
g flag since we can either just test for the existence of a match (no
g flag) or that the string starts/ends how we expect (using
$, groups, and ranges).
We could have avoided the entire problem if we just removed the
g flag from the regex itself.
const regex = /test/ // returns true regex.test('test123') // returns true 🎉 regex.test('test123')
Personally, I think this is the ideal solution—we're using the method as intended, and our regexes reflect the way that we intend them to be used.
Sometimes this isn't perfectly possible though. Perhaps you're using the regex in another context where it needs to have the
g flag. Perhaps you're not entirely sure which regex will be passed in to your code and you just want to make it more predictable.
If the regex absolutely has to have the
g flag, we can provide some much-needed purity to our code by using the slightly less ergonomic String.prototype.match method and casting it into a
// note that we're using the `g` flag again const regex = /test/g const str = 'test123' // returns true Boolean(str.match(regex)) // returns true 🎉 Boolean(str.match(regex))
It's not as ergonomic, but it still provides the same
boolean result. Since
string.match returns an array of matches and
null if there's no matches in the string, we can turn this into a
boolean just by wrapping it in the
Boolean function to convert it.
regex.test(str) mutates a
lastIndex property. The next time you call
regex.test it starts testing
lastIndex instead of the beginning. This means that multiple calls to
regex.test might return different results, even if they were called with the same arguments.
Feel free to hit me up on my Twitter or LinkedIn with any thoughts or if you enjoyed this article. If you found a typo or have some feedback for improvement also feel free to submit a pull request. Thanks for reading! 🎉