GeezerVison is showing github.com — docs: update `eslint` versions in examples (#20664) · eslint/eslint@eab65c7
File treeExpand file treeCollapse file tree Open diff view settings custom-rule-tutorial-code integration-tutorial-code
Expand file treeCollapse file tree Open diff view settings Collapse file Copy file name to clipboardExpand all lines: docs/_examples/custom-rule-tutorial-code/package.json +2-2Lines changed: 2 additions & 2 deletions | Original file line number | Diff line number | Diff line change |
|---|
| 10 | 10 | "eslint-plugin" | 11 | 11 | ], | 12 | 12 | "peerDependencies": { | 13 | | - "eslint": ">=9.0.0" | | 13 | + "eslint": ">=10.0.0" | 14 | 14 | }, | 15 | 15 | "scripts": { | 16 | 16 | "test": "node enforce-foo-bar.test.js" | 17 | 17 | }, | 18 | 18 | "author": "", | 19 | 19 | "license": "ISC", | 20 | 20 | "devDependencies": { | 21 | | - "eslint": "^9.35.0" | | 21 | + "eslint": "^10.0.0" | 22 | 22 | } | 23 | 23 | } |
Collapse file Copy file name to clipboardExpand all lines: docs/_examples/integration-tutorial-code/package.json +1-1Lines changed: 1 addition & 1 deletion | Original file line number | Diff line number | Diff line change |
|---|
| 11 | 11 | "author": "", | 12 | 12 | "license": "ISC", | 13 | 13 | "dependencies": { | 14 | | - "eslint": "^9.35.0" | | 14 | + "eslint": "^10.0.0" | 15 | 15 | } | 16 | 16 | } |
Collapse file Copy file name to clipboardExpand all lines: docs/src/extend/custom-rule-tutorial.md +4-4Lines changed: 4 additions & 4 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -381,7 +381,7 @@ To publish a plugin containing a rule to npm, you need to configure the `package | 381 | 381 | 1. `"name"`: A unique name for the package. No other package on npm can have the same name. | 382 | 382 | 1. `"main"`: The relative path to the plugin file. Following this example, the path is `"eslint-plugin-example.js"`. | 383 | 383 | 1. `"description"`: A description of the package that's viewable on npm. | 384 | | -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. | | 384 | +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. | 385 | 385 | 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. | 386 | 386 |
| 387 | 387 | 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 | 398 | 398 | "scripts": { | 399 | 399 | "test": "node enforce-foo-bar.test.js" | 400 | 400 | }, | 401 | | - // Add eslint>=9.0.0 as a peer dependency. | | 401 | + // Add eslint>=10.0.0 as a peer dependency. | 402 | 402 | "peerDependencies": { | 403 | | - "eslint": ">=9.0.0" | | 403 | + "eslint": ">=10.0.0" | 404 | 404 | }, | 405 | 405 | // Add these standard keywords to make plugin easy to find! | 406 | 406 | "keywords": [ | @@ -411,7 +411,7 @@ A complete annotated example of what a plugin's `package.json` file should look | 411 | 411 | "author": "", | 412 | 412 | "license": "ISC", | 413 | 413 | "devDependencies": { | 414 | | - "eslint": "^9.0.0" | | 414 | + "eslint": "^10.0.0" | 415 | 415 | } | 416 | 416 | } | 417 | 417 | ``` | |
Collapse file Copy file name to clipboardExpand all lines: docs/src/extend/plugins.md +1-1Lines changed: 1 addition & 1 deletion - Display the source diff
- Display the rich diff
| 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 | ``` | |
|