-
-
Notifications
You must be signed in to change notification settings - Fork 69
import/no-unresolved
unable to resolve @atlaskit/pragmatic-drag-and-drop
’s nested imports after upgrading 3.8.7 → 4.2.4
#409
New issue
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
Comments
Please provide a GitHub repository reproduction. |
![]() Just a quick look, it seems resolving cc @Boshen I'll try whether can fix it by myself. |
Closing due to lack of reproduction, feel free to provide a reproduction, then I'll take a look again. |
@JounQin sorry for the delay. i finally put together a minimal reproducible example: https://github.com/acusti/eslint-import-resolver-typescript-repro it’s using latest yarn (v4.9.1) and PnP, but i’m not sure if that’s required to make it reproducible. it might be only reproducible from a |
Thanks for providing the reproduction, I'll take a look when I'm free, or contributing will be much appreciated. |
i am using @atlassian/pragmatic-drag-and-drop, which exposes a number of nested import targets. when i upgrade
eslint-import-resolver-typescript
from 3.8.7 to 4.2.4, i get errors when trying to import from any of those targets:here are the lines in question:
using v3.8.7, there are no linting errors. i am using v1.5.2 of
@atlaskit/pragmatic-drag-and-drop
. myeslint.config.js
file configures the import/resolver like so:and i am using eslint v9.23.0
let me know if there’s anything else that would be useful for me to provide, and thanks for this excellent project! i had a lot of struggles with eslint and typescript and the
import/*
eslint rules before finding it and getting it configured correctly.The text was updated successfully, but these errors were encountered: