'markdown/markdown' was not found.
See original GitHub issueGetting the following error:
Error: ESLint configuration of processor in '.eslintrc#overrides[0]' is invalid: 'markdown/markdown' was not found.
Reproduction repo here:
- Clone
- npm ci
npm run lint
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
"bin / bash: markdown: command not found" - Stack Overflow
This error occurs when you do not have a markdown parser installed. Installing one is simple with brew. From the command line:.
Read more >eslint-plugin-markdown - npm Package Health Analysis - Snyk
The npm package eslint-plugin-markdown was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as...
Read more >SDS - Troubleshooting in R Markdown - GitHub Pages
it means that R cannot find any object in its environment called my_object . Make sure that my_object is created in the Markdown...
Read more >ngx-markdown - npm
Angular library that uses marked to parse markdown to html combined with Prism.js for synthax highlights. Latest version: 15.0.0, ...
Read more >0 - LaTeX Stack Exchange
input.markdown.lua not found" error into pdf ... pandoc.exe --pdf-engine-opt=-shell-escape --from=markdown --output=test.pdf mini.md ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I released v2.0.0-alpha.0 over the weekend, and the readme in
master
includes a note about it being a prerelease as well as instructions to install the@next
dist-tag and a migration guide. I’ve switched the default branch back tomaster
because I’d like people to try the v2 release if they’re willing.The other projects under the ESLint org do all development in
master
, so I don’t want to break that convention. However, I’ve created av1
branch off of the last non-breaking commit and made it the default branch in GitHub so that the docs reflect the most recent release. Once I get the docs and migration together for the new processor API, I’ll do an alpha and switch the default branch back tomaster
.