Is it possible to report unused exports in entry files in folders that are not being 'used' or 'imported' throughout the project? about knip HOT 9 CLOSED

Thanks for your detailed reporting. I'm working on #140 which is related, and I'm planning to have a fix in the coming days.

from knip.

I've re-introduced the --include-entry-exports flag in v2.14.0-next.0.

Any chance you could try it out on your project(s)?

You can install with e.g. npm install -D knip@next

from knip.

Thanks for trying so quickly.

Yeah I was kinda afraid of such results, that's why I did a pre-release first.

It is expected, but not desired. I think I need to make a difference between regular source code entry files versus entry files added by plugins. WIP :)

from knip.

I've released another next pre-release.

I should add that for files referenced in scripts like this:

"module1": "tsx src/module1/index.ts"

The unused exports won't be reported. Maybe these should be added to entry explicitly? E.g.:

{
  "entry": ["src/*/index.ts"],
  "project": ["src/**/*.ts"]
}

from knip.

Gave it a little more thought and I think it makes sense to include script files when using the --include-entry-exports flag.

By the way, I didn't mean to say you should include scripts in both entry config and npm scripts. Only in one place should be enough indeed.

from knip.

@webpro thanks for your effort, everything works now 🎉

from knip.

@webpro thanks for the quick fix
I have tried on the above example, it works as expected now

But I have tried on another project

and I am getting prettier lint-staged and vite config files as reported
on knip: 2.13.0 I wasn't getting this

knip: 2.14.0-next.0

Unused exports (5)
default  .prettierrc.cjs       
default  knip.ts               
default  lint-staged.config.cjs
LABELS   src/cli/index.ts  ---> this is reported correctly
default  vite.config.ts

Is it expected?

from knip.

@webpro thank you, I have tried the latest version and it works as you mentioned, but in my opinion this behaviour is a bit confusing

in package.json I have

{
  "scripts": {
    "start:cli": "tsx src/cli/index.ts",
    "start:server": "tsx src/server/index.ts"
  }
}

and in knip:

{
  "entry": ["src/*/index.ts"],
  "project": ["src/**/*.ts"]
}

and with this setup src/cli/index.ts and src/server/index.ts are not reported, if I remove these scripts from package.json everything is reported correctly.

But, I think, it's useful to keep thoose scripts in package.json, unfortunately this breaks knip --include-entry-exports flag reporting

Is there any solution here?

from knip.

🚀 This issue has been resolved in v2.14.0. See Release 2.14.0 for release notes.

from knip.