How it is compared to depcheck? about vscode-dependency-cruiser HOT 2 CLOSED

Hi,
I need to check a little bit more depcheck but this plugin is based on this other tool: npmjs.com/package/dependency-cruiser which is mainly for js/TS ecosystem.

It's using that under the hood to do the analysis. My goal is to provide a UI on top of it that would let you filter and organize the automatic visualization to make more sense of it. The main goal was to give you a good way of visualizing dependencies. I find this sometimes hard on TS/JS.

What would be some use cases you had in mind?

from vscode-dependency-cruiser.

Sorry for the latency. I looked into dependency-cruiser and now I understand that there are different. dependency-cruiser builds TypeScript import graphs, while depcheck is focused on detecting which package.json dependencies are in usage, which are missing in package.json but used in the code and finally which are not used and can be removed. It mainly focused on "just find any usage", without even reporting location in files. It looked promising since it has special detectors, e.g. it can detect that dependency referened in package.json script.

I just wanted to try it on real projects, so built https://github.com/zardoy/vscode-depcheck and even UI is absolutely different

I'll probably try to improve to location detections and finally make it possible to bundle..

from vscode-dependency-cruiser.