fix: search npmjs registry for community plugins #1258
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Kap currently uses npms to index community plugins but it appears the project and its API are abandoned since around 2023. This means that new community plugins aren't being indexed or shown in Kap's plugin list since then, and existing plugins' versions aren't being updated. It's very broken. And it's one of Kap's best features!
Solution
This PR fixes the issue and restores community plugins(!) by using npmjs' registry to index plugins instead. I've tested and confirmed the change works with the kap plugin I'm currently building, kap-share. I can't wait to share it (plz merge 🤞)!
Screenshot of fixed build