docs: update to eslint v9 in custom-rule-tutorial (#18383)

* docs: update rule tester options in custom-rule-tutorial

Fixes #18382

* chore: update examples

* chore: update more places to eslint v9

docs/_examples/custom-rule-tutorial-code/enforce-foo-bar.test.js

@@ -1,4 +1,4 @@
-/** 
+/**
  * @fileoverview Tests for enforce-foo-bar.js rule.
  * @author Ben Perlmutter
 */
@@ -10,7 +10,7 @@ const fooBarRule = require("./enforce-foo-bar");
 const ruleTester = new RuleTester({
  // Must use at least ecmaVersion 2015 because
  // that's when `const` variable were introduced.
- parserOptions: { ecmaVersion: 2015 }
+ languageOptions: { ecmaVersion: 2015 }
 });
 
 // Throws error if the tests in ruleTester.run() do not pass
@@ -31,4 +31,4 @@ ruleTester.run(
  }
 );
 
-console.log("All tests passed!");
+console.log("All tests passed!");

docs/_examples/custom-rule-tutorial-code/package.json

@@ -1,5 +1,6 @@
 {
  "name": "eslint-plugin-example",
+ "private": true,
  "version": "1.0.0",
  "description": "ESLint plugin for enforce-foo-bar rule.",
  "main": "eslint-plugin-example.js",
@@ -9,14 +10,14 @@
  "eslint-plugin"
  ],
  "peerDependencies": {
- "eslint": ">=8.0.0"
+ "eslint": ">=9.0.0"
  },
  "scripts": {
  "test": "node enforce-foo-bar.test.js"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
- "eslint": "^8.36.0"
+ "eslint": "^9.1.1"
  }
-}
+}

docs/_examples/integration-tutorial-code/package.json

@@ -1,5 +1,6 @@
 {
  "name": "_integration-tutorial-code",
+ "private": true,
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
@@ -10,6 +11,6 @@
  "author": "",
  "license": "ISC",
  "dependencies": {
- "eslint": "^8.39.0"
+ "eslint": "^9.1.1"
  }
 }

docs/src/extend/custom-rule-tutorial.md

@@ -217,7 +217,7 @@ const fooBarRule = require("./enforce-foo-bar");
 const ruleTester = new RuleTester({
  // Must use at least ecmaVersion 2015 because
  // that's when `const` variables were introduced.
- parserOptions: { ecmaVersion: 2015 }
+ languageOptions: { ecmaVersion: 2015 }
 });
 
 // Throws error if the tests in ruleTester.run() do not pass
@@ -362,7 +362,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": ">=8.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": ">=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. `"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:
@@ -379,9 +379,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>=8.0.0 as a peer dependency.
+ // Add eslint>=9.0.0 as a peer dependency.
  "peerDependencies": {
- "eslint": ">=8.0.0"
+ "eslint": ">=9.0.0"
  },
  // Add these standard keywords to make plugin easy to find!
  "keywords": [
@@ -392,7 +392,7 @@ A complete annotated example of what a plugin's `package.json` file should look
  "author": "",
  "license": "ISC",
  "devDependencies": {
- "eslint": "^8.36.0"
+ "eslint": "^9.0.0"
  }
 }
 ```