[workaround found] Vague error - error with no location

[sanjarcode]

Describe the bug

An error is shown but the trace, or at least location of the error is not shown

TypeError: list.map is not a function OK, but where??

Reproduction

No repro, need to fix the error reporting sentence.

System Info

Mac, Vite, React

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[github-actions]

Hello @sanjarcode. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with needs reproduction will be closed if they have no activity within 3 days.

[Botuca]

Hi @sanjarcode, I had the same issue today in the company's project. After debugging for a while, I managed to resolve it in two ways. My friend and colleague @elionaimelo helped me fix the problem.

In my project, I was using Vue version 3.5.12, Vitest version 2.0.5, and vue/coverage-v8 version 2.0.5 as well. After updating Vue to version 3.5.13 and updating both Vitest and vue/coverage-v8 to version 2.1.6, my project successfully ran the unit tests using the command npx vitest.

Another way to resolve the issue is to simply install the package @vue/server-renderer and keep the current versions of Vue and Vitest that you’re already using.

From what I understand, the new version of Vitest (2.1.6) now implicitly installs the @vue/server-renderer package, which is necessary for running unit tests correctly.

[LitenApe]

Just wanted to mention that this issue might be related JSDOM. JSDOM's dependency, nwsapi, was recently updated, and a similar issue appeared there, so it might be related

dperini/nwsapi#135

[sheremet-va]

From what I understand, the new version of Vitest (2.1.6) now implicitly installs the @vue/server-renderer package, which is necessary for running unit tests correctly.

Vitest doesn't install any vue packages

[CreeTar]

I have this same issue after updating to JSDOM v25 due to the punycode warning from it's tough-cookie dependency. Now all my vitest-unit tests using vue testutils are not working anymore with the same error message. The error is thrown in the jsdom-package when a selector is called, for me it's this line of code: mountedComponent.getComponent(VTextField).get('label');
Techstack is Vue3, Vuetify, Vite

[pratyakash]

I am also facing the same kind of Error with Next JS 14 and Vitest

[sanjarcode]

Turns out the problem is with jsdom, or atleast u can fix it by patching it.

Patch (1 line of code): jsdom/jsdom#3797

The error goes away after this.