Could we use Alpine as replacement for Vue in non-build scenarios?

[hongquan]

Some feature needs to be implemented as JS code, like the dropdown menu. I want to stay away from jQuery and adopt reactive programming, which most of modern frameworks (React, Angualar, Vue, Svelte) are pursuiting.

Looking into current eventyay-talk code base, I found that:

• It is mixing Vue 2 and Vue 3, by various authors.
• It is applied strict CSP, which stops Vue 2 from working.
• There are some code written with Vue 2 by Pretalx authors, and to overcome the CSP, they whitelist CSP for pages (CfP editor) with Vue 2.
• The Vue 3 code is written for "schedule editor" by TMA dev. Vue 3 is not stopped by CSP, but they had to create a whole subproject for one page.

To continue with the development, there are some way:

1. Develop with Vue 2 and disable CSP entirely, because the global dropdown is supposed to appear on all pages.
2. Allow to use AlpineJS. AlpineJS has a variant for CSP. Alpine is very like Vue but smaller, suitable for multiple small apps without the "build process".
3. Create another Vue 3 subproject like what TMA dev did.
4. Rework on the Vue 3 app (made by TMA dev) to make it work for multi-page app.

I favor the AlpineJS approach.
I used to mention Vue 3, but we can use Vue 3 full power if our app is Single-Page-Application.

[norbusan]

Can we update the Vue2 code to Vue3?

[hongquan]

@norbusan Yes, for the current Vue 2 code which pretalx authors did, we can just wait for pretalx upstream to update to Vue 3.
My concern is our own features that we develop ourselves. We may implement it in AlpineJs, or with Vue 3, but with Vue 3, there are two options:

• Create a subproject for each feature, even if the feature is small.
• Reorganize Vue 3 code which TMA dev did, to convert it to multi-page app.

[mariobehling]

Yes, VueJS, create a subproject for each feature, even if the feature is small.