You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have found that two circumstances need to exist for this error to appear:
For some custom component:
a. The component is given a v-for prop to render it multiple times,
b. The component is given a ref prop to put the array of components in, and
c. The name passed into ref is defined as a ref in <script setup> block; and
A variable is defined in the <script setup> block and is used in v-bind in the <style> block.
Given where the error occurs, it seems item 2 is more of a culprit than item 1. However, item 1 still needs to exist, so it must be at least somewhat at fault. How, though, I have no idea.
The text was updated successfully, but these errors were encountered:
I hava the same problem.The parentNode is "null" causes this problem. But when I use MutationObserver to monitor the parentNode, I find it has never been modified.
Vue version
3.3.8
Link to minimal reproduction
https://github.com/noahgregory-basis/nuxt-test
Steps to reproduce
npm run dev
to start the dev server.console.log
line inBar.vue
and save to trigger hot module reload.Uncaught (in promise) TypeError: Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.
This appears to happen in the
useCssVars
helper function. Specifically inside theonMounted
callback, at the line (as seen below in the bundle):What is expected?
No error occurs when hot-reloading.
What is actually happening?
Error occurs when hot-reloading.
System Info
No response
Any additional comments?
I have found that two circumstances need to exist for this error to appear:
a. The component is given a
v-for
prop to render it multiple times,b. The component is given a
ref
prop to put the array of components in, andc. The name passed into
ref
is defined as a ref in<script setup>
block; and<script setup>
block and is used inv-bind
in the<style>
block.Given where the error occurs, it seems item 2 is more of a culprit than item 1. However, item 1 still needs to exist, so it must be at least somewhat at fault. How, though, I have no idea.
The text was updated successfully, but these errors were encountered: