Skip to content
Discussion options

You must be logged in to vote

I resolved the issue with a suggestion from google gemini search response.

The correct configuration looks like this, where markdown.configs.processor is required. If markdown.configs.processor is necessary, imo, it should shown in migration guide and README.md (it is not)

flat style,

[
  ...markdown.configs.processor,
  {
    files: ["*.md"],
    language: "markdown/gfm",
    plugins: {markdown}
  },
  ...rest
]

defineConfig style,

defineConfig[
  markdown.configs.processor,
  {
    files: ["*.md"],
    language: "markdown/gfm",
    plugins: {markdown}
  },
  ...rest
]

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by iambumblehead
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant