False positive results with imports via paths alias

[jtbandes]

Hello @nadeesha! I just tried using ts-prune for the first time on this repository and I'm confused by the results, because many/most of them seem to be false positives.

The repo is a monorepo with several packages. This is the command I ran to try out ts-prune on the biggest package (here's the tsconfig.json):

yarn dlx ts-prune -p packages/studio-base/tsconfig.json

The results look like this:

packages/studio-base/src/App.tsx:31 - default
packages/studio-base/src/AppSetting.ts:5 - AppSetting
packages/studio-base/src/index.ts:11 - App
packages/studio-base/src/index.ts:12 - NetworkInterface
packages/studio-base/src/index.ts:12 - OsContext
....a bunch more from index.ts....
packages/studio-base/src/OsContextSingleton.ts:13 - default
packages/studio-base/src/Workspace.tsx:142 - default
....lots more results....

For example, the first result is the default export of App.tsx. This is re-exported from index.tsx, so I wouldn't expect it to be considered unused.

For another example let's look at the default export from OsContextSingleton.ts — this is imported as import OsContextSingleton from "@foxglove/studio-base/OsContextSingleton"; in several places (here's one example).

Is it our paths setting that's throwing off ts-prune? Or am I doing something else wrong?

Thanks for your help! This seems like a great project and it would be awesome if it worked for us.

[connorads]

Hey @jtbandes, I had the same experience. Did you manage to resolve it?

PS. This is my first time using GitHub discussions. I guess it might be like StackOverflow and I'm not supposed to put questions here 😬

[jtbandes]

Nope, I didn’t learn anything more after I posted this 😕

[connorads]

For anyone who discovers this thread: Conversation moved to issue #139