How to re initialize Alpine JS v3 in LivewView

[polygonpusher]

It would look as if there is a new way to initialize Alpine js
https://alpinejs.dev/essentials/installation#as-a-module

The key takeaway is that now you have to call Alpine.start() after you import.

I’ve noticed that the use of Alpine.clone does not seem to be enough alone anymore.
My Alpine js works for everything outside of LV but for dom elms inside they get blown aways after the call to clone. I bet I’m just missing one more step that’s required to re initialize the alpine js elements.

Has anyone else figured this out yet?

Edit: calling Alpine.start from the console does seem to work to re initialize but I guess its not enough to call it from onBeforeElUpdated? I guess I should find a onAfterElUpdated

Edit: I’ve tried to call from both onElUpdated and onNodeAdded with no luck

Edit Edit:
The solution was seen here.
Its in the way we watch the dom that has changed.

Shadowed assigns with AlpineJS v3 and Phoenix LiveView 0.15

We’re running into an odd problem with AlpineJS and Phoenix LiveView, whereby Alpine reacts to the previous value of an assign when it changes. For example, with the following LEEx (lifted verbatim from Patrick Thompson’s excellent blog post: <div id="counter" x-data="{count: <%= count %>}"> <h1>The assigns count is: <span><%= @count %></span></h1> <h1>The alpine count is: <span x-text="count"></span></h1> </div> With Alpine v2, both the assigns count and Alpine count are kept in sync when…

      onBeforeElUpdated(from, to) {
        if (!window.Alpine) return;
        if (from.nodeType !== 1) return;
        // AlpineJS v2
        if (from.__x) window.Alpine.clone(from.__x, to);
        // AlpineJS v3
        if (from._x_dataStack) window.Alpine.clone(from, to);
      },

[polygonpusher]

The solution is simply

      onBeforeElUpdated(from, to) {
        if (from._x_dataStack) {
          window.Alpine.clone(from, to);
          window.Alpine.initTree(to)
        }
      },

[cigrainger]

We used that solution and it caused some major problems. Namely with mark.js. But generally things like empty selections.