docs: update eslint versions in examples (#20664)

lumirlumir · web-flow · commit eab65c700ebb · 2026-03-22T20:52:31.000+01:00
* chore: update `eslint` versions in examples

* wip
diff --git a/docs/_examples/custom-rule-tutorial-code/package.json b/docs/_examples/custom-rule-tutorial-code/package.json
@@ -10,14 +10,14 @@
     "eslint-plugin"
   ],
   "peerDependencies": {
-    "eslint": ">=9.0.0"
+    "eslint": ">=10.0.0"
   },
   "scripts": {
     "test": "node enforce-foo-bar.test.js"
   },
   "author": "",
   "license": "ISC",
   "devDependencies": {
-    "eslint": "^9.35.0"
+    "eslint": "^10.0.0"
   }
 }
diff --git a/docs/_examples/integration-tutorial-code/package.json b/docs/_examples/integration-tutorial-code/package.json
@@ -11,6 +11,6 @@
   "author": "",
   "license": "ISC",
   "dependencies": {
-    "eslint": "^9.35.0"
+    "eslint": "^10.0.0"
   }
 }
diff --git a/docs/src/extend/custom-rule-tutorial.md b/docs/src/extend/custom-rule-tutorial.md
@@ -381,7 +381,7 @@ To publish a plugin containing a rule to npm, you need to configure the `package
 1. `"name"`: A unique name for the package. No other package on npm can have the same name.
 1. `"main"`: The relative path to the plugin file. Following this example, the path is `"eslint-plugin-example.js"`.
 1. `"description"`: A description of the package that's viewable on npm.
-1. `"peerDependencies"`: Add `"eslint": ">=9.0.0"` as a peer dependency. Any version greater than or equal to that is necessary to use the plugin. Declaring `eslint` as a peer dependency requires that users add the package to the project separately from the plugin.
+1. `"peerDependencies"`: Add `"eslint": ">=10.0.0"` as a peer dependency. Any version greater than or equal to that is necessary to use the plugin. Declaring `eslint` as a peer dependency requires that users add the package to the project separately from the plugin.
 1. `"keywords"`: Include the standard keywords `["eslint", "eslintplugin", "eslint-plugin"]` to make the package easy to find. You can add any other keywords that might be relevant to your plugin as well.
 
 A complete annotated example of what a plugin's `package.json` file should look like:
@@ -398,9 +398,9 @@ A complete annotated example of what a plugin's `package.json` file should look
   "scripts": {
     "test": "node enforce-foo-bar.test.js"
   },
-  // Add eslint>=9.0.0 as a peer dependency.
+  // Add eslint>=10.0.0 as a peer dependency.
   "peerDependencies": {
-    "eslint": ">=9.0.0"
+    "eslint": ">=10.0.0"
   },
   // Add these standard keywords to make plugin easy to find!
   "keywords": [
@@ -411,7 +411,7 @@ A complete annotated example of what a plugin's `package.json` file should look
   "author": "",
   "license": "ISC",
   "devDependencies": {
-    "eslint": "^9.0.0"
+    "eslint": "^10.0.0"
   }
 }
 ```
diff --git a/docs/src/extend/plugins.md b/docs/src/extend/plugins.md
@@ -385,7 +385,7 @@ In order to make your plugin available publicly, you have to publish it on npm.
     ```json
     {
     	"peerDependencies": {
-    		"eslint": ">=9.0.0"
+    		"eslint": ">=10.0.0"
     	}
     }
     ```

Original file line number	Diff line number	Diff line change
`@@ -11,6 +11,6 @@`
`11`	`11`	`"author": "",`
`12`	`12`	`"license": "ISC",`
`13`	`13`	`"dependencies": {`
`14`		`- "eslint": "^9.35.0"`
	`14`	`+ "eslint": "^10.0.0"`
`15`	`15`	`}`
`16`	`16`	`}`
Original file line number	Diff line number	Diff line change
`@@ -385,7 +385,7 @@ In order to make your plugin available publicly, you have to publish it on npm.`
`385`	`385`	```json
`386`	`386`	`{`
`387`	`387`	`"peerDependencies": {`
`388`		`- "eslint": ">=9.0.0"`
	`388`	`+ "eslint": ">=10.0.0"`
`389`	`389`	`}`
`390`	`390`	`}`
`391`	`391`	```