Skip to content

Conversation

@dan-os
Copy link

@dan-os dan-os commented Oct 12, 2025

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

Screenshot

@dan-os dan-os force-pushed the fix/plugin-package-registry branch 2 times, most recently from 412cf28 to f5683b3 Compare October 12, 2025 01:38
@dan-os
Copy link
Author

dan-os commented Oct 12, 2025

+1 for #1234 to be merged too as it appears the current CI build system is broken.

Edit: Using some help from #1234 I've fixed the build system with minimal changes.

@dan-os dan-os force-pushed the fix/plugin-package-registry branch 2 times, most recently from cc95823 to c407c26 Compare October 12, 2025 02:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant