This repository has been archived by the owner on Jan 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 262
How to track down and fix circular dependency detected error? #661
Labels
Comments
ejmurra
changed the title
How to track down circular dependency detected error?
How to track down and fix circular dependency detected error?
Aug 11, 2016
I think this might have been fixed in NPM v3 with flattening, but might not work in v2. That said, this behaviour in Typings may be able to be improved so that during resolution it can reference the parent type and during compilation it re-uses previous paths. |
I get the same issue on with |
Anyone is welcome to submit a PR, I haven't had time to fix it. It's be a matter of re-using the pointer during |
bsouthga
added a commit
to tyranid-org/tyranid
that referenced
this issue
Aug 27, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a project that is broken into two parts - a "core" package and a CLI that uses the core. Both are authored in Typescript.
While trying to install the core typings for use in the CLI with
typings install npm:lede
I have been battling a circular dependency error:My "core" package is dependent on the following:
In my best effort to figure out what was going on, I added the high-tech debug statements
just above this line in the typings-core source and then reran the command and piped stdout to a file.
The majority of that file is unimportant but the important bit is here at the end:
So it seems to me that I am depending on a package (babelify) that depends on babel-core which depends on babel-register, which in turn depends on babel-core - thus the circular dependency! However I find it curious that this circular dependency isn't thrown by npm itself and it has me wondering if typings isn't resolving this as it should be or if I have just royally messed something up.
The text was updated successfully, but these errors were encountered: