Thanks to visit codestin.com
Credit goes to github.com

Skip to content

incompatible with markdown files and eslint-plugin-mdx out of box #412

@JounQin

Description

@JounQin

Similar to #411, this is because of eslint-plugin-markdown@1

.md are parsable as estree by eslint-plugin-mdx and eslint-plugin-markdown@2 has changed to use virtual filename instead, so the md to babel mapping becomes incorrect then.

I don't know if you think this as BREAKING CHANGE for eslint-plugin-markdown@1 users, but they can simply set parser: 'markdown' if we remove the incorrect mapping.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions