Support for import path aliases about knip HOT 6 CLOSED

Absolutely. This has actually been in some old version, but it will be back as a new feature after v1 lands.

from knip.

The feature to add paths has been added in v1.6.0. Also see the docs at https://github.com/webpro/knip#paths.

from knip.

I am not entirely sure but I think knip only checks for tsconfig.json but not other variations of that filename right?

With https://nx.dev/ which we use, it's common to have a tsconfig.base.json (notice the name) at the root of the project.

When running knip without any config, I see our custom lib names as "Unlisted or unresolved dependencies".
When basically copying and pasting the paths from compilerOptions.paths to knip.json paths, these unresolved deps are gone. So I think it would make sense to support tsconfig.base.json out of the box.

from knip.

Additionally, we have imports like ~/components/plans-details/TierCircle which show up as unresolved.

The tsconfig.paths config for that is:

"~/*": ["./*"]

Just putting my 2 cents here since its related to import path aliases improvements 😄

from knip.

I am not entirely sure but I think knip only checks for tsconfig.json but not other variations of that filename right?

With https://nx.dev/ which we use, it's common to have a tsconfig.base.json (notice the name) at the root of the project.

When running knip without any config, I see our custom lib names as "Unlisted or unresolved dependencies". When basically copying and pasting the paths from compilerOptions.paths to knip.json paths, these unresolved deps are gone. So I think it would make sense to support tsconfig.base.json out of the box.

The default is indeed tsconfig.json (in root and/or in any workspace package). This can be overridden using -t or --tsConfig. When there is an extends in the TS config, that should work fine, too. You should not need to manually copy over the paths when using TS config.

from knip.

Going to close this one as I think the original issue is resolved.

from knip.