search

Thunberg087 / vue-fragment

a very candide fragment component for Vue.js
http://jsfiddle.net/cdkn5wL3/
670 stars 51 forks source link

Issue with vue-fragment 1.5.2 #61

Open sardor01 opened 3 years ago

sardor01 commented 3 years ago

I'm getting this issue with the new version of vue-fragment (1.5.2):

[Vue warn]: Error in nextTick: "NotFoundError: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node."

DOMException: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node. vue-fragment-error

svtokarevsv commented 3 years ago

same. Started happening in 1.5.2. Will revert to previous version for now.

elderdog commented 3 years ago

same. Better to roll back to v1.5.1

Dylan-bak commented 3 years ago

i have same problem this version caused a bug on my proj

evgencode commented 3 years ago

same problem

mschiele commented 3 years ago

same problem here

fxmanu commented 3 years ago

Same here. The MR https://github.com/Thunberg087/vue-fragment/pull/48 seems to break having a fragment as a root element in a dynamically added or removed component.

I rolled back to v1.5.1 and look forward to having fixed this issue in a future release. Thanks for this library :-)

victorgarciaesgi commented 3 years ago

Is every one using Nuxt? I have this error since i updated Nuxt to 2.15.x

victorgarciaesgi commented 3 years ago

but as @fxmanu said, reverting back to v.1.5.1 fix the problem for me!

fxmanu commented 3 years ago

Is every one using Nuxt? I have this error since i updated Nuxt to 2.15.x

No, I don't.

dineshtrivedi commented 3 years ago

Same here. I also rolledback to 1.5.1.

I am using Quasar, @victorgarciaesgi

victorgarciaesgi commented 3 years ago

Ok just to know if it was nuxt related but it seems not!

sardor01 commented 3 years ago

same. Better to roll back to v1.5.1

For now, this seems to solve the problem.

korelstar commented 3 years ago

same. Better to roll back to v1.5.1

For now, this seems to solve the problem.

Please keep the issue open since the problem still exists for the latest release. Other people will find this known problem faster and can better track if it is fixed.

woganmay commented 3 years ago

This caused a production issue for us today. It looks like the bump from 1.5.1 to 1.5.2 introduces a lot more than just backward-compatible bug fixes :)

BaileyJM02 commented 3 years ago

This is a duplicate of #32.

volarname commented 2 years ago

same prob with vue-fragment 1.5.2 and vue 2.6.14

yoonwooseong commented 2 years ago

If the occurrence point is a