vue-fragment
vue-fragment copied to clipboard
Errors on navigation/unloading (v1.5.2)
I've been using 1.5.1 happily for a while but needed to update to use 1.5.2 for the :html binding. Now whenever I navigate (using vue-router) and content is unloaded I get the following.

The page does not successfully load. This is in a NuxtJS (2.14.12) environment and the error happens when I am using any fragments on the page whether I actually use the new :html binding or not. If I go back to 1.5.1 the error goes away but my :html bound fragments do not work and so I have to use contained ones which mess up the legacy style definitions I am trying to use.
I will try and create a CodePen but at the moment I'm not really sure how to do routing in CP.
Have the same issue with nuxt 2.15.3 on two different projects.
Same here
anyone have solution?
I was able to do everything I needed in the end by migrating to vue-frag as discussed in this issue (https://github.com/Thunberg087/vue-fragment/issues/32)
same here on nuxt 2.14.12
nothing new, think we have to wait for vue3 and nuxt3 so fragment is included. Workaround as @web2wire mentioned use vue-frag, but there you have the problem that the wrapper element is unmounted when page is mounted. Conts classes from parent effects only when page is fully loaded, leads to jumping components
This is a duplicate of #32 and can be fixed without changing dependencies. (See #32)
I was able to do everything I needed in the end by migrating to vue-frag as discussed in this issue (#32)
For anybody experiencing this issue migrating to vue-frag has fixed the problem for me also. Seems this package does not handle conditional rendering very well