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
$ ls
eslint.config.js node_modules package.json package-lock.json test.md
$ eslint
/home/ether/Desktop/try_eslint/test.md
6:1 error 'test' is not defined no-undef
✖ 1 problem (1 error, 0 warnings)
If I comment out the processor: 'markdown/markdown' line in my eslint.config.js, I get this instead:
$ eslint
/home/ether/Desktop/try_eslint/test.md
3:1 error Duplicate heading "Title" found markdown/no-duplicate-headings
✖ 1 problem (1 error, 0 warnings)
What did you expect to happen?
I expect to get both linting errors at the same time.
What actually happened?
I either get linting applied to the contents outside of the code blocks, or inside of the code blocks, depending on whether processor is specified in my eslint.config.js.
Environment
ESLint version: 9.13.0
@eslint/markdown version: 6.2.1
Node version: 23.1.0
npm version: 10.9.0
Operating System: Ubuntu 24.04
Which language are you using?
commonmark
What did you do?
Configuration
Markdown file
Actual behavior
$ ls eslint.config.js node_modules package.json package-lock.json test.md $ eslint /home/ether/Desktop/try_eslint/test.md 6:1 error 'test' is not defined no-undef ✖ 1 problem (1 error, 0 warnings)
If I comment out the
processor: 'markdown/markdown'
line in myeslint.config.js
, I get this instead:$ eslint /home/ether/Desktop/try_eslint/test.md 3:1 error Duplicate heading "Title" found markdown/no-duplicate-headings ✖ 1 problem (1 error, 0 warnings)
What did you expect to happen?
I expect to get both linting errors at the same time.
What actually happened?
I either get linting applied to the contents outside of the code blocks, or inside of the code blocks, depending on whether
processor
is specified in myeslint.config.js
.Link to Minimal Reproducible Example
https://github.com/ehmicky/eslint-markdown-bug
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: