Doesn't seem to work out of the box

[Zamiell]

Greetings,

I tried giving this plugin a test drive on my existing repository, but it didn't work, even with a red herring that I inserted:

export function foo(): void {}

For troubleshooting purposes, I tried again on a fresh "Hello World"-style repository, and I couldn't get it to work there either. I've uploaded this repository here: https://github.com/Zamiell/test Running lint.sh does not yield any errors.

So it looks like this plugin isn't working at all.

Can you confirm?

[GollyJer]

I'm in the same boat. Was excited to get this going but it seems it's not working.

[wcandillon]

Indeed, the plugin is a bit broken at the moment, the main issue is that I'm not sure how to "cache" the dependency tree. If we do it for every file change, it would take too much resources.

The issue you seem to be experiencing is the opposite, the dependency tree.

[Zamiell]

Any updates on this? I've resorted to running ts-prune independently, but it would be very useful to be able to integrate all-the-tools inside of eslint.

[wcandillon]

Unfortunately, we don't have a good solution on how to run this within eslint.

[xanderfehsenfeld]

Indeed, the plugin is a bit broken at the moment, the main issue is that I'm not sure how to "cache" the dependency tree. If we do it for every file change, it would take too much resources.

Although it is too resource-intensive, do you mind fixing the yarn dependency so others such as myself can clone, build, and run the repo?

[Zamiell]

@xanderfehsenfeld Don't use this repo and use ts-prune instead, it is great and I would recommend it.

[wcandillon]

indeed this was a failed experiment as it's not really possible to integrate ts-prune with eslint