search

Thunberg087 / vue-fragment

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

DOM errors because of vue-fragment #62

Closed sardor01 closed 1 year ago

sardor01 commented 3 years ago

I think I'm having issues related to DOM in my app

image

bgriggs1 commented 3 years ago

Same. Using v-show vs. v-if fixed a few cases, but it's pervasive for almost any reactive DOM updates.

tomchiverton commented 3 years ago

Duplicate of #61

sardor01 commented 3 years ago

Duplicate of #61

It's not a duplicate; In https://github.com/Thunberg087/vue-fragment/issues/61 I addressed errors in new version of vue-fragment, but here I used vue-fragment v1.5.1 and still had DOM related issues.

Lionad-Morotar commented 3 years ago

Same

Tchoupinax commented 3 years ago

Hello,

Same issue met. Someone knows why ? The node to be removed is not a child of this node.


client.js?06a0:103 DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at Object.removeChild (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:5703:8)
    at removeNode (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:5874:15)
    at remove$$1 (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:5863:9)
    at removeAndInvokeRemoveHook (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:6150:9)
    at removeVnodes (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:6119:11)
    at updateChildren (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:6225:7)
    at patchVnode (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:6309:29)
    at VueComponent.patch [as __patch__] (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:6472:9)
    at VueComponent.Vue._update (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:3942:19)
    at VueComponent.updateComponent (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:4054:10)```
BaileyJM02 commented 3 years ago

This is a duplicate of #32 and can be fixed without changing dependencies. (See #32)

@Sardor01, I believe you may have incorrectly altered your package.json file.