We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I created a reproduction for a Next.js project with support for MDX files: https://github.com/chrisweb/eslint-import-resolver-typescript_mdx_reproduction
After migrating to eslint-import-resolver-typescript 3.8.x a new "import/no-unresolved" linting error started to appear
It could be related to #363 (if there is a PR to fix 363 I will check if it also solves the problem mentioned here)
I was hoping the #360 PR (from the #359 ticket) would fix the problem but it did not
The text was updated successfully, but these errors were encountered:
cc @carlocorradini
Sorry, something went wrong.
No branches or pull requests
I created a reproduction for a Next.js project with support for MDX files: https://github.com/chrisweb/eslint-import-resolver-typescript_mdx_reproduction
After migrating to eslint-import-resolver-typescript 3.8.x a new "import/no-unresolved" linting error started to appear
It could be related to #363 (if there is a PR to fix 363 I will check if it also solves the problem mentioned here)
I was hoping the #360 PR (from the #359 ticket) would fix the problem but it did not
The text was updated successfully, but these errors were encountered: