regexExecutors

Reports String.prototype.match calls that can be replaced with RegExp.prototype.exec.

✅ This rule is included in the ts stylisticStrict presets.

Reports calls to String.prototype.match() that should use RegExp.prototype.exec() instead. When a regular expression does not have the global flag (g), both methods behave identically, but exec() is clearer in intent and may be slightly faster.

Examples

String Literal with Regex Literal

❌ Incorrect

const result = "something".match(/thing/);

✅ Correct

const result = /thing/.exec("something");

Variable with Regex

❌ Incorrect

const text = "something";
const result = text.match(/pattern/);

✅ Correct

const text = "something";
const result = /pattern/.exec(text);

RegExp Constructor

❌ Incorrect

const result = "something".match(new RegExp("thing"));

✅ Correct

const result = new RegExp("thing").exec("something");

Global Flag (Valid)

Using the global flag with match() is valid because it returns all matches:

const allMatches = "one two three".match(/\w+/g);

Options

This rule is not configurable.

When Not To Use It

If you prefer consistent use of String.prototype.match() regardless of whether the global flag is present, you may disable this rule.

Further Reading

• MDN: String.prototype.match()
• MDN: RegExp.prototype.exec()

Equivalents in Other Linters

• ESLint: @typescript-eslint/prefer-regexp-execregexp/prefer-regexp-exec