-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
import/no-cycle fails when tsconfig has multiple extends #2890
Comments
See:
We should update tsconfig-paths to 4.2.0 or later. It's currently 3.14.2. |
Closed
This comment was marked as spam.
This comment was marked as spam.
Unfortunately, we can't; see #2447. If tsconfig backports this support to v3, or lowers their supported node versions, we can get the functionality here. |
Also see #2751 |
Fix for tsconfig-paths instead: dividab/tsconfig-paths#260 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Typescript 5 now supports multiple extends in tsconfig,
but when i have multiple extends i get this error
The text was updated successfully, but these errors were encountered: