Resolving Knip error with automatic Imports using unplugin-vue-components about knip HOT 5 CLOSED

Alright, cool!

I appreciate the feedback, at the very least it serves as a reminder that custom resolvers could be a very useful feature (perhaps a bit similar to how custom compilers fit in pretty well).

from knip.

Probably the easiest way is to add the auto-imported components to the entry paths.

from knip.

Does that mean if a component is no longer used, I won't get a Knip error?
I've tested it, and I don't get any errors, do you think there might be a way to trigger an error if a component is not used (thus not imported)?

from knip.

Does that mean if a component is no longer used, I won't get a Knip error?

No, entry files are glob matches, even zero matches is not an error. And they don't need to be import-ed by another module.

I've tested it, and I don't get any errors, do you think there might be a way to trigger an error if a component is not used (thus not imported)?

Since the components are auto-imported, there's no way for Knip to understand this. Knip basically works from entry files and then following import statements.

Custom resolvers don't work great with Knip I'm afraid. I don't currently see an easy way to add a custom resolver. But feel free to explore this, I'm open to something clean and maintainable.

Or... don't use magic and explicitly import components.

from knip.

Thanks for the details and quick responses!

I think we can close this for now; I'm not ready to explore more on this

from knip.