The "extends": "eslint:recommended"
property in a configuration file enables this rule.
The --fix
option on the command line can automatically fix some of the problems reported by this rule.
Regular expressions can be very complex and difficult to understand, which is why it’s important to keep them as simple as possible in order to avoid mistakes. One of the more error-prone things you can do with a regular expression is to use more than one space, such as:
var re = /foo bar/;
In this regular expression, it’s very hard to tell how many spaces are intended to be matched. It’s better to use only one space and then specify how many spaces are expected, such as:
var re = /foo {3}bar/;
Now it is very clear that three spaces are expected to be matched.
This rule disallows multiple spaces in regular expression literals.
Examples of incorrect code for this rule:
/*eslint no-regex-spaces: "error"*/ var re = /foo bar/; var re = new RegExp("foo bar");
Examples of correct code for this rule:
/*eslint no-regex-spaces: "error"*/ var re = /foo {3}bar/; var re = new RegExp("foo {3}bar");
If you want to allow multiple spaces in a regular expression, then you can safely turn this rule off.
This rule was introduced in ESLint 0.4.0.
© JS Foundation and other contributors
Licensed under the MIT License.
https://eslint.org/docs/rules/no-regex-spaces