Does this have support (or is there a plan to have support) for something similar to knip plugins? For example, a webpack.config.js file might import some packages or files, and the knip webpack plugin is able to parse it to understand these dependencies, and feed that information back into all the checks (e.g. unused files, undeclared package.json dependencies, etc.).
Just curious. It's great to have a performance-focused option in this space either way!
Not yet, currently it supports typescript path aliases and ESM imports/exports map. So industry standard I would say.
I don't think making plugins system is feasible because project focuses on performance. It's build in Go, so compiled language, so it's not easy to extend it like you can with JavaScript based tools.
But definitely I would like to support some reasonable amount of leading frameworks/build tools if they define some syntax / resolving mechanism that is beyond ESM specification.
jayu_dev|1 day ago
I don't think making plugins system is feasible because project focuses on performance. It's build in Go, so compiled language, so it's not easy to extend it like you can with JavaScript based tools.
But definitely I would like to support some reasonable amount of leading frameworks/build tools if they define some syntax / resolving mechanism that is beyond ESM specification.