docs: split out linter/nested-config.md

Author: Boshen

.vitepress/config/en.ts

@@ -49,8 +49,8 @@ export const enConfig = defineLocaleConfig("root", {
                   link: "/docs/guide/usage/linter/config",
                 },
                 {
-                  text: "Command-line Interface",
-                  link: "/docs/guide/usage/linter/cli",
+                  text: "Nested Configs",
+                  link: "/docs/guide/usage/linter/nested-config",
                 },
                 {
                   text: "Rules",
@@ -64,6 +64,10 @@ export const enConfig = defineLocaleConfig("root", {
                   text: "Automatic Fixes",
                   link: "/docs/guide/usage/linter/automatic-fixes",
                 },
+                {
+                  text: "CLI reference",
+                  link: "/docs/guide/usage/linter/cli",
+                },
                 {
                   text: "Configuration file reference",
                   link: "/docs/guide/usage/linter/config-file-reference",

src/docs/guide/usage/linter/config.md

@@ -249,60 +249,3 @@ You can ignore certain patterns of files by configuring the `ignorePatterns` pro
   "ignorePatterns": ["vendor", "test/snapshots/**", "test.js"],
 }
 ```
-
-## Nesting configuration files
-
-> [!WARNING]
-> This is currently an experimental feature and may have bugs. To enable it, pass the `--experimental-nested-config` option in the command-line.
-
-It is possible to have multiple configuration files within the same project, and Oxlint will automatically detect the presence of these files and use them in addition to the top-level configuration file. The files must be named `.oxlintrc.json` for this to work.
-
-For example, consider the following project structure:
-
-```
-my-project/
-├── .oxlintrc.json
-├── src/
-│   ├── index.js
-├── package1/
-│   ├── .oxlintrc.json
-│   └── index.js
-└── package2/
-    ├── .oxlintrc.json
-    └── index.js
-```
-
-Oxlint will always use the nearest configuration file to the file currently being processed and use that for linting. In the example hierarchy above, that means:
-
-- `src/index.js` will be linted using `my-project/.oxlintrc.json`
-- `package1/index.js` will be linted using `my-project/package1/.oxlintrc.json`
-- `package2/index.js` will be linted using `my-project/package2/.oxlintrc.json`
-
-Configuration files are not automatically merged, and the configuration in a child configuration file will not affect the parent configuration. However, options passed in the command-line will override any configuration file, regardless of whether it is in the parent or child directory. In addition, using the `--config` option to specify a singular file for configuration will disable the use of nested configuration files.
-
-## Extending configuration files
-
-Files can use configuration from other files by using the `extends` property in a configuration file. The value of the `extends` property is an array of file paths to other configuration files, which are resolved relative to the location of the configuration file. Files may be called anything and do not need to be called `.oxlintrc.json`, but still need to be valid JSON configuration files.
-
-```jsonc
-// oxlint-typescript.json
-{
-  "plugins": ["typescript"],
-  "rules": {
-    "typescript/no-explicit-any": "error"
-  }
-}
-// .oxlintrc.json
-{
-  "extends": ["oxlint-typescript.json"],
-  "rules": {
-    "no-unused-vars": "warn"
-  }
-}
-```
-
-Not all properties can be extended, but the following properties are supported:
-
-- `rules`
-- `plugins`
-- `overrides`

src/docs/guide/usage/linter/nested-config.md

@@ -0,0 +1,63 @@
+---
+outline: [2, 3]
+editLink: false
+---
+
+# Nested Configs
+
+## Nesting configuration files
+
+> [!WARNING]
+> This is currently an experimental feature and may have bugs. To enable it, pass the `--experimental-nested-config` option in the command-line.
+
+It is possible to have multiple configuration files within the same project, and Oxlint will automatically detect the presence of these files and use them in addition to the top-level configuration file. The files must be named `.oxlintrc.json` for this to work.
+
+For example, consider the following project structure:
+
+```
+my-project/
+├── .oxlintrc.json
+├── src/
+│   ├── index.js
+├── package1/
+│   ├── .oxlintrc.json
+│   └── index.js
+└── package2/
+    ├── .oxlintrc.json
+    └── index.js
+```
+
+Oxlint will always use the nearest configuration file to the file currently being processed and use that for linting. In the example hierarchy above, that means:
+
+- `src/index.js` will be linted using `my-project/.oxlintrc.json`
+- `package1/index.js` will be linted using `my-project/package1/.oxlintrc.json`
+- `package2/index.js` will be linted using `my-project/package2/.oxlintrc.json`
+
+Configuration files are not automatically merged, and the configuration in a child configuration file will not affect the parent configuration. However, options passed in the command-line will override any configuration file, regardless of whether it is in the parent or child directory. In addition, using the `--config` option to specify a singular file for configuration will disable the use of nested configuration files.
+
+## Extending configuration files
+
+Files can use configuration from other files by using the `extends` property in a configuration file. The value of the `extends` property is an array of file paths to other configuration files, which are resolved relative to the location of the configuration file. Files may be called anything and do not need to be called `.oxlintrc.json`, but still need to be valid JSON configuration files.
+
+```jsonc
+// oxlint-typescript.json
+{
+  "plugins": ["typescript"],
+  "rules": {
+    "typescript/no-explicit-any": "error"
+  }
+}
+// .oxlintrc.json
+{
+  "extends": ["oxlint-typescript.json"],
+  "rules": {
+    "no-unused-vars": "warn"
+  }
+}
+```
+
+Not all properties can be extended, but the following properties are supported:
+
+- `rules`
+- `plugins`
+- `overrides`