How to find third-party Alpine plugins? Should we set a repo/npm package naming convention to make it easier to search for plugins?

[philwolstenholme]

I love how easy it is to extend Alpine now, and I've got an idea for a third-party plugin of my own. I want to check that no one else has made a plugin that duplicates my idea (they probably haven't, but in the future this will be more likely to be a problem).

Other than asking here, or checking repos like https://github.com/alpine-collective/awesome#extensions--plugins I am not sure how to get a list of Alpine plugins 'in the wild'. I tried searching Github for Alpine.plugin( and filtering it to JS results, but there are quite a lot of false positives where the the core Alpine plugins come up in results, or some things not related to Alpine(JS) appear. I also tried searching for "Alpine.directive(" OR "Alpine.magic(" and limiting it to JavaScript results but that mostly returned forks of Alpine itself.

I was wondering if there are any unofficial or official standards on how the plugin should be named? I am thinking of Babel plugins where there is a convention to use names like babel-plugin-foo or babel-plugin-bar, and Parcel uses a similar system:

Plugins should be named with the prefix parcel-plugin- or @your-scope/parcel-plugin-, e.g. parcel-plugin-foo or @your-scope/parcel-plugin-foo. Any dependencies listed in package.json with these prefixes will automatically be loaded during initialization.

I think the main use of standardised names in Parcel is to allow autoloading, but it also makes it much easier to find plugins via Github or npm. Someone could then use the Github or npm API to make a list of all the publicly available Alpine packages.