composition-api VS Alpine.js

Composition API (now built-in): Composition API is a built-in feature of Vue 3 and is currently available to Vue 2 through the officially maintained @vue/composition-api plugin. In Vue 3, it's mainly used together with the syntax in single-report additives. Here is a basic instance of a issue using Composition API:

√ What would you like to build? » App with Quasar CLI, let's go! √ Project folder: ... quasar-qrcode-scanner √ Pick Quasar version: » Quasar v1 (Vue 2) √ Pick script type: » Typescript √ Package name: ... quasar-qrcode-scanner √ Project product name: (must start with letter if building mobile apps) ... Quasar QR Code Scanner √ Project description: ... A Quasar Project √ Author: ... √ Pick a Vue component style: » Composition API (recommended) (https://github.com/vuejs/composition-api) √ Pick your CSS preprocessor: » Sass with SCSS syntax √ Pick a Quasar components & directives import strategy: (can be changed later) » * Auto-import in-use Quasar components & directives - also treeshakes Quasar; minimum bundle size √ Check the features needed for your project: » ESLint √ Pick an ESLint preset: » Prettier

I'd just found out about this back port of the Composition API to Vue 2 (https://github.com/vuejs/composition-api). What's your experience with that? Is it stable enough to use in a production project with +1000 users? Or is more experimental?

While Vue 3 has had a paradigma change by switching to the Composition API as the primary API, you still can use the "old" Options API which stays mostly unchanged to Vue 2. And vice-versa Vue 2 actually supports most of the Composition API when you include an additional plugin: https://github.com/vuejs/composition-api

Is it even worth it to use https://github.com/vuejs/composition-api or should i migrate to vue 3. I'm only using vue 2 so i can use the vuetify calendar component.

Npm package: @vue/composition-api

If you can’t migrate to Vue 3 today, then you can still use the Composition API already. You can do this by installing the official Composition API Vue 2 Plugin.

I see that the @vue/composition-api also admits to having some performance overhead when used with Vue 2. And it appears to have quite a list of its own gotchas, judging from the README.

For what it's worth most of Vue 3's features can be backported to Vue 2 apps by including the @vue/composition-api package. I agree with the other comment, the v2 docs will get you very far.

Alpine.js for reactive frontend

✨ In recent months, I have been developing web projects using GOTTHA stack: Go + Templ + Tailwind CSS + htmx + Alpine.js. As soon as I'm ready to talk about all the subtleties and pitfalls, I'll post it on my social networks.

> But honestly, torn towards htmx but undecided.

We are in the middle of migrating from our monster react application into server rendered pages (with jinja2). The velocity at which we are able to ship and the reduction of complexity has been great so far.

Managing client side state for simple things like (is the dropdown open/closed), listening to keyboard events and such can be done with something like alpine-js [1] without all the baggage that something like react brings.

It appears this is already the trend with JS frameworks too - with server side rendering being the new norm.

[1] https://alpinejs.dev/

Sure, you can use any number of JS-avoidance libraries. I'm a fan of Turbo, and there's also htmx, Unpoly, Alpine, hyperscript, swup, barba.js, and probably others.

Direct DOM, but with a library. Specifically AlpineJS since it follows Vue closely in design practices allowing me to scale into a full web application if necessary (basically swapping to Vue takes minimal work). The Morph plugin is specifically what I like using.

If you want more details on the initial setup I encourage you to take a look at the Part I that covers more of the initial implementation. For this portion, I added Prisma as an ORM, a frontend style library called Tachyons, and AlpineJS to handle any client-side interactions. I did this to avoid needing to add a client-side bundler to the build and instead just rely on plain old module imports to compose the frontend. This is now the default for Rails and it is quite nice to not need any additional build tools for the client.

- [swallow-pywebview](https://github.com/rangwea/swallow-pywebview)： Base on [pywebview](https://pywebview.flowrl.com/) using Python，the frontend base on [alpinejs](https://alpinejs.dev/) and [tailwindcss](https://tailwindcss.com/)。

If you’ve followed our other tutorials, you might be familiar with Alpine.js. It’s a lightweight JavaScript library that allows you to add interactivity to your site without writing a single line of JavaScript. It’s incredibly easy to use, and we’ll show you how to make the animation trigger when the user scrolls to it.

The approach is not new, essentially a variation of Knockout, Alpine, and similar "JS-in-HTML" approaches.