Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Apply suggestions from code review
  • Loading branch information
silverwind authored Nov 10, 2025
commit 49355e44e7cb4c928dbd83474c841e22227a23fa
2 changes: 1 addition & 1 deletion docs/user-guide/options.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ This option should be a string that resolves to a JS module that exports a [Post

If you want to lint two or more different languages, you can combine `customSyntax` with the [`overrides`](./configure.md#overrides) configuration property.

Using the Node.js API, the `customSyntax` option can also accept a [Syntax object](https://postcss.org/docs/how-to-write-custom-syntax#syntax) or a function with those properties. Stylelint treats the `parse` property as a required value. Also, Stylelint supports syntax modules written in ESM.
Using the Node.js API, the `customSyntax` option can also accept a [Syntax object](https://postcss.org/docs/how-to-write-custom-syntax#syntax). Stylelint treats the `parse` property as a required value. Also, Stylelint supports syntax modules written in ESM.

> [!NOTE]
> Stylelint can provide no guarantee that core rules work with custom syntaxes.
Expand Down