You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -83,10 +83,14 @@ The example of configuration file:
83
83
84
84
See [test configuration file][test-config] or [style folder][style-folder] for more examples.
85
85
86
-
CLI argument `--config` is not mandatory.
87
-
If it is not provided, `markdownlint-cli` looks for file `.markdownlint.json`/`.markdownlint.yaml`/`.markdownlint.yml` in current folder, or for file `.markdownlintrc` in current or all upper folders.
88
-
The algorithm is described in details on [rc package page][rc-standards].
89
-
If `--config` argument is provided, the file must be valid JSON, JSONC, or YAML.
86
+
The CLI argument `--config` is not required.
87
+
If it is not provided, `markdownlint-cli` looks for the file `.markdownlint.json`/`.markdownlint.yaml`/`.markdownlint.yml` in current folder, or for the file `.markdownlintrc` in the current or all parent folders.
88
+
The algorithm is described in detail on the [`rc` package page][rc-standards].
89
+
If the `--config` argument is provided, the file must be valid JSON, JSONC, JS, or YAML.
90
+
JS configuration files contain JavaScript code, must have the `.js` extension, and must export (via `module.exports = ...`) a configuration object of the form shown above.
91
+
A JS configuration file may internally `require` one or more npm packages as a way of reusing configuration across projects.
92
+
93
+
> JS configuration files must be provided via the `--config` argument; they are not automatically loaded because running untrusted code is a security concern.