Skip to content
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

Closed
EladBezalel opened this issue Oct 1, 2023 · 5 comments
Closed

import/no-cycle fails when tsconfig has multiple extends #2890

EladBezalel opened this issue Oct 1, 2023 · 5 comments

Comments

@EladBezalel
Copy link

Typescript 5 now supports multiple extends in tsconfig,
but when i have multiple extends i get this error

The "path" argument must be of type string. Received an instance of Array
Occurred while linting ...
   Rule: "import/no-cycle"
@domdomegg
Copy link

See:

We should update tsconfig-paths to 4.2.0 or later. It's currently 3.14.2.

@domdomegg

This comment was marked as spam.

@ljharb
Copy link
Member

ljharb commented Nov 25, 2023

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.

@domdomegg
Copy link

Also see #2751

@domdomegg
Copy link

Fix for tsconfig-paths instead: dividab/tsconfig-paths#260

@ljharb ljharb closed this as completed in 48fec35 Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants