Tried to use the tool without much success

It shows that little despite AppManager having dozens of imports

For reference the command I'm using is
depcruise --max-depth 99 --output-type dot .\src\scripts\main.ts | dot -T svg > dependencygraph.svg
When I try to use it on the all folder the result is empty, meaning when I run:
depcruise --max-depth 99 --output-type dot src/scripts | dot -T svg > dependencygraph.svg
It should show dependencies
It doesn't show dependencies
From the diagram it seems the AppManager module cannot be found. This can have several causes. Assuming that AppManager exists, and the import reference in src/scripts/main is correct it might be dependency-cruiser can't find the typescript compiler (it searches for it in the same spot it's installed) - your second sample suggests this to be the case.
To know for sure: what does depcruise --info tell in your installation? If dependency-cruiser _could_ find the typescript compiler it'll look something like this (mark the โ in front of typescript and the extensions associated with typescript):
Supported:
If you need a supported, but not enabled transpiler ('โ' below), just install
it in the same folder dependency-cruiser is installed. E.g. 'npm i livescript'
will enable livescript support if it's installed in your project folder.
Transpilers:
โ javascript (>es1)
โ coffee-script (>=1.0.0 <2.0.0)
โ coffeescript (>=1.0.0 <3.0.0)
โ livescript (>=1.0.0 <2.0.0)
โ typescript (>=2.0.0 <4.0.0)
Extensions:
โ .js
โ .mjs
โ .jsx
โ .vue
โ .ts
โ .tsx
โ .d.ts
โ .ls
โ .coffee
โ .litcoffee
โ .coffee.md
โ .csx
โ .cjsx
Typescript shows with โ but typescript is already installed in node_modules? (I verified using npm list)
I tried installing dependency-cruiser locally to see if that would help but did nothing.
node_modules and the binary is in ./node_nodules/.bin/depcruise) and typescript is installed locally, dependency-cruiser picks up that one.Note that if you use depcruise on the command line you're using the globally installed one. So even if you install dependency-cruiser locally, it'll use the global one, and pick up any global compiler.
So you can do one of two things:
./node_modules/.bin/depcruise directly (it's where the _scripts_ section of your package.json will look) or use npm's npx : npx depcruise ...HTH
Hi @Ivanca I assume the answer in the previous comment sufficed to resolve the issue. If that isn't the case, feel free to re-open the issue with more details.
I'll add an entry to the FAQ as this is bound to come up more often.
Most helpful comment
node_modulesand the binary is in./node_nodules/.bin/depcruise) and typescript is installed locally, dependency-cruiser picks up that one.Note that if you use
depcruiseon the command line you're using the globally installed one. So even if you install dependency-cruiser locally, it'll use the global one, and pick up any global compiler.So you can do one of two things:
./node_modules/.bin/depcruisedirectly (it's where the _scripts_ section of your package.json will look) or use npm's npx :npx depcruise ...HTH