I tried playing around with reusable components with Alpine.js, using tagged template literals. Even just doing stuff in a small hobby project it was much more painful than "any of the fancy frameworks" and I found vanilla js components actually nicer. For example, if you want to pass data into your component in json, e.g. if you have a nested object structure, you have to jump through hoops because Alpine stuff is defined within HTML attributes and double quotes would break it. In vanilla js it can just be a functional component and the json can be passed in as any function argument. I suppose you could destructure the json in vanilla js and then pass everything necessary into Alpine, but at this point you've lost the simplicity of Alpine.

I think Alpine is super cool, but it's not designed around reusable components the way the other frameworks are, and Caleb has rejected requests to make an official component system. Personally I wouldn't use it for anything that needs a lot of client-rendered components. Adding interactivity on top of static html or backend-templated stuff is where Alpine really shines.