Enable eslint-plugin-mdx for linting .mdx files and a true showcase with ignoreRemarkConfig option enabled so remark-cli still will be used

[JounQin]

ignoreRemarkConfig must be enabled because remark-lint is not compatible with mdx v3 yet

[ChristianMurphy]

Hey @JounQin! 👋
Are you announcing you are working on a show case?
Or are you asking a question about remark-lint?
I'm not sure I follow either the announcement or the question.

[JounQin]

Sorry, I don't quite sure which part? The benefit is eslint-mdx can help linting jsx rules for mdx documents, and xo should support adding custom eslint plugins?

For faster or slower, I believe linting is more important. Otherwise we should just drop all linting tools?

[wooorm]

You can have no food. You can have too much food. Between that there is enough food.

I think xo and prettier and remark/remark-lint are useful in the 500+ project I work on.
There are other linters that could be used. To use them, I need good reasons.

Do you have examples of things that are bad now? Things that eslint-mdx would solve?

[JounQin]

The bad part is the ES syntaxes in mdx files are not linted at all? It could have some issues, but it's not must be there. Some issues maybe already be resolved via human testing/reporting or PR reviews, while eslint-plugin-mdx makes them lintable as tools. That's why eslint-mdx is built for?

[wooorm]

There is almost no JavaScript in the MDX files in mdx-js/mdx. The JavaScript that they contain doesn’t change often.

Do you have examples of things that are bad now, that eslint-mdx would solve?

[JounQin]

Let me try to raise a PR with eslint-plugin-mdx and eslint-plugin-react enabled to confirm.