diff --git a/‎docs/src/extend/selectors.md‎
Lines changed: 10 additions & 6 deletions b/‎docs/src/extend/selectors.md‎
Lines changed: 10 additions & 6 deletions
diff --git a/‎package.json‎
Lines changed: 1 addition & 1 deletion b/‎package.json‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎tests/lib/rules/no-restricted-syntax.js‎
Lines changed: 13 additions & 0 deletions b/‎tests/lib/rules/no-restricted-syntax.js‎
Lines changed: 13 additions & 0 deletions
@@ -33,7 +33,7 @@ The following selectors are supported:
 - wildcard (matches all nodes): `*`
 - attribute existence: `[attr]`
 - attribute value: `[attr="foo"]` or `[attr=123]`
-- attribute regex: `[attr=/foo.*/]` <sub>(with some [known issues](#known-issues))</sub>
+- attribute regex: `[attr=/foo.*/]`
 - attribute conditions: `[attr!="foo"]`, `[attr>2]`, `[attr<3]`, `[attr>=2]`, or `[attr<=3]`
 - nested attribute: `[attr.level2="foo"]`
 - field: `FunctionDeclaration > Identifier.id`
@@ -147,21 +147,25 @@ Or you can enforce that calls to `setTimeout` always have two arguments:
 
 Using selectors in the `no-restricted-syntax` rule can give you a lot of control over problematic patterns in your codebase, without needing to write custom rules to detect each pattern.
 
-### Known issues
+### Using regular expressions
 
-Due to a [bug](https://github.com/estools/esquery/issues/68) in [esquery](https://github.com/estools/esquery), regular expressions that contain a forward-slash character `/` aren't properly parsed, so `[value=/some\/path/]` will be a syntax error. As a [workaround](https://github.com/estools/esquery/issues/68), you can replace the `/` character with its unicode counterpart, like so: `[value=/some\u002Fpath/]`.
+You can use regular expressions in attribute selectors. For example, the following selector matches all `Identifier` nodes with a `name` value that starts with "foo":
 
-For example, the following configuration disallows importing from `some/path`:
+```text
+Identifier[name=/^foo/]
+```
+
+You can also use forward slashes in your regular expressions. For example, the following configuration disallows importing from `some/path`:
 
 ```json
 {
 	"rules": {
 		"no-restricted-syntax": [
 			"error",
-			"ImportDeclaration[source.value=/^some\\u002Fpath$/]"
+			"ImportDeclaration[source.value=/^some\\/path$/]"
 		]
 	}
 }
 ```
 
-Note that the `\` character needs to be escaped (`\\`) in JSON and string literals.
+Note that the `/` character inside the regular expression needs to be escaped (`\/`) so it is not interpreted as the end of the regular expression. Additionally, because the selector is inside a JSON string, the backslash character itself needs to be escaped (`\\`).
@@ -123,7 +123,7 @@
     "eslint-scope": "^9.1.0",
     "eslint-visitor-keys": "^5.0.0",
     "espree": "^11.1.0",
-    "esquery": "^1.5.0",
+    "esquery": "^1.7.0",
     "esutils": "^2.0.2",
     "fast-deep-equal": "^3.1.3",
     "file-entry-cache": "^8.0.0",
 
@@ -361,5 +361,18 @@ ruleTester.run("no-restricted-syntax", rule, {
 				},
 			],
 		},
+		{
+			code: "import values from 'some/path';",
+			options: ["ImportDeclaration[source.value=/^some\\/path$/]"],
+			errors: [
+				{
+					messageId: "restrictedSyntax",
+					data: {
+						message:
+							"Using 'ImportDeclaration[source.value=/^some\\/path$/]' is not allowed.",
+					},
+				},
+			],
+		},
 	],
 });