I went the Alpine route when LiveView was new and without any JS integration outside of Hooks, for micro interactions Alpine made so much sense (and I was familiar with Vue API which Alpine kinda of mimics).
I later dropped it in favour of just plain LiveView.JS usage and/or combined with Hooks.

Why? Well, because of the CSP (Content-Security Policy), reference: CSP — Alpine.js

In order for Alpine to be able to execute plain strings from HTML attributes as JavaScript expressions, for example x-on:click="console.log()" , it needs to rely on utilities that violate the “unsafe-eval” content security policy.

I’m not comfortable with the trade back nor with the CSP violation, so I preferred to go the %JS{} / Hook routes.

Glad for your contribution, think that is a good idea. The Phoenix components PETAL framework makes use of Alpine, maybe it can also serve as inspiration for people following that route.

You are right, %JS can’t replace Alpine at all, and probably it never will. That is why we have hooks. I dont think hooks are overkill at all, simply a necessity and generally sprinkling some hooks are all we need in LV land. When hooks get co-located I think we really wont need Alpine at all.

But Alpine is very practical indeed inspite of the CSP violation.

The initial entries are now available (in the README.md):

https://github.com/liveview-alpine/integration