Open quisido opened 6 months ago
@quisido Can you please add a reproduction for this? As long as a document exists, JSDOM implicitly creates document.body
for you.
@quisido Can you please add a reproduction for this? As long as a document exists, JSDOM implicitly creates
document.body
for you.
Are you unable to reproduce it? I've hit this in two separate projects just by setting container to document.
As far as I'm aware, using container: document
in any existing test is the only step required to reproduce this.
Two points here:
@MatanBobi Running into same issue as described here. Here is reproducible example (clone from your StackBlitz but switched from vitest to jest): https://stackblitz.com/edit/stackblitz-starters-3sze3m?file=app%2Flayout.spec.tsx
@m-zuro Thanks. In the reproduction you've attached here, the test isn't passing:
● Test Suite › Test
Expected value undefined Received: undefined Message: Unable to find an element with the text: Test. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body />
So I think there's a misconfiguration there.
@MatanBobi sorry, copy/paste job. Updated now, can you re try pls?
● Test Suite › Test
Expected value undefined
Received:
undefined
Message:
null is not an object (evaluating 'document.body.removeChild')
Just opening this for tracking with the associated PR: #1330 .
When:
(Untested: This bug may require that
Component
render a<body>
element.)Then:
Because:
If we first check that
document.body
is not null, then this error will not occur.