Context
We use mise to manage our dev env and have a monorepo. We added dependency-cruiser to our setup and ran it. We were under the assumption that ✔ no dependency violations found meant there weren't any violations. But we were wrong! It turned out that dependency-cruiser needs a typescript compiler in the same folder as where it is installed. This behaviour is fine, but it could be made more apparant.
Expected Behavior
It would be nice if it could at least show a warning if it finds files it can handle, but doesn't have a compiler for them. for example:
Warning: Typescript files found, but missing compiler
@see https://github.com/sverweij/dependency-cruiser/blob/main/doc/faq.md#q-typescript-coffeescript-livescript-or-vue-single-file-component-sfc-dependencies-dont-show-up-how-can-i-fix-that
Current Behavior
It just shows ✔ no dependency violations found
Possible Solution
Considered alternatives
Context
We use mise to manage our dev env and have a monorepo. We added dependency-cruiser to our setup and ran it. We were under the assumption that
✔ no dependency violations foundmeant there weren't any violations. But we were wrong! It turned out that dependency-cruiser needs a typescript compiler in the same folder as where it is installed. This behaviour is fine, but it could be made more apparant.Expected Behavior
It would be nice if it could at least show a warning if it finds files it can handle, but doesn't have a compiler for them. for example:
Warning: Typescript files found, but missing compiler
@see https://github.com/sverweij/dependency-cruiser/blob/main/doc/faq.md#q-typescript-coffeescript-livescript-or-vue-single-file-component-sfc-dependencies-dont-show-up-how-can-i-fix-that
Current Behavior
It just shows
✔ no dependency violations foundPossible Solution
Considered alternatives