Make some dependencies pluggable

[dehmer]

Depending on the application, kbar may introduce dependencies for functionality already covered by a different set of libraries. For application maintenance this seems suboptimal. Especially when dependencies are more on the heavier side and are slow to respond to recent developments (e.g. React 18).

Specifically in our application we already use

• react-cool-virtual (vs. react-virtual, now @tanstack/react-virtual@beta)
• react-fast-compare (vs. fast-equals)
• fuse.js (vs. command-score?)

I might look into introducing the required abstract interfaces, but since I’m not a great fan of TypeScript I’m not sure if this goes anywhere in the near future.

[stale]

Hey! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.