Cannot read properties of undefined (reading 'getRootNode')
See original GitHub issueHi there 👋🏻 ,
I hope it is the right place to ask, and I apologize if not. I’m currently trying to bump version of happy-dom from 2.51.0 to a greater one using vitest & vue 3 but I’m facing the following error:
happy-dom version: 3.1.0 (I’ve tried multiple version between this one and 2.51.0)
vitest version: 0.10.0
It seems to be related to usage of @headlessui/vue (version 1.5.0) but I haven’t found yet the root cause.
Thanks in advance for your help, wish you a nice day ☀️
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:8 (3 by maintainers)
Top Results From Across the Web
[BUG] - Cannot read property 'getRootNode' of undefined ...
Expectation: it should generate the audits Actual: it throws an exception error TypeError: Cannot read property 'getRootNode' of undefined ...
Read more >Uncaught TypeError: Cannot read property 'getRootNode' of ...
I'm new to extjs, can any one aware of this issue. Uncaught TypeError: Cannot read property 'getRootNode' of undefined. Store Ext.define('my.
Read more >Node.getRootNode() - Web APIs | MDN
An object that sets options for getting the root node. The available options are: composed : A boolean value that indicates whether the...
Read more >Uncaught TypeError: Cannot read property of null - iDiallo
All this means is that you are trying to access a property of an object that is undefined. These usually happens when we...
Read more >uncaught typeerror: cannot read properties of null ... - You.com
The "Cannot read property 'forEach' of undefined" error often occurs when trying to access an array index that doesn't exist. index.js const arr...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Here is a codesandbox with the minimal possible code to produce this error. Indeed, it only happens when running a second test (when adding a
.onlyto the second test, it does not happen).I can confirm this is related to
happy-dom. I changed thevitestenvironment tojsdom, and all tests passed. In my case, it also happens when running a second test.