How to re initialize Alpine JS v3 in LivewView

It would look as if there is a new way to initialize Alpine js

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 :man_shrugging: 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 :frowning:

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

      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);
      },
1 Like

The solution is simply

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

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