jestjs/jest

[Bug]: Jest v30: setupFilesAfterEnv fails with mounted volume path (unrs-resolver unsupported construct)

Open

#15923 opened on Dec 21, 2025

View on GitHub
 (9 comments) (0 reactions) (0 assignees)TypeScript (45,361 stars) (6,653 forks)batch import
Bug ReportHelp WantedNeeds TriagePinnedWindows

Description

Version

30.0.2

Steps to reproduce

After upgrading from Jest v29 to v30 in my restricted corporate environment - Virtual Machine with user directory as mounted volume, tests fail to load @testing-library/jest-dom even though it is installed. Jest throws a validation error on configuration file:

Module @testing-library/jest-dom in the setupFilesAfterEnv option was not found.

This only started happening after upgrading to v30.

After looking in to the source code, it seems that there is an error coming out from the unrs-resolver, which tries to resolve mounted volume with a path starting with \\?:

Error: Path "\\?\Volume{c79c005d-0000-0000-0000-100000000000}\" contains unsupported construct.

Expected behavior

Jest should be able to resolve node_modules or files on mounted volumes.

Actual behavior

Jest throws a validation error on configuration file:

Module @testing-library/jest-dom in the setupFilesAfterEnv option was not found.

Additional context

No response

Environment

System:
    OS: Windows 10 10.0.17763
    CPU: (32) x64 Intel(R) Xeon(R) Gold 6240R CPU @ 2.40GHz
  Binaries:
    Node: 18.20.8 - D:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Users\vmuser\AppData\Roaming\npm\yarn.CMD
    npm: 10.8.2 - D:\Program Files\nodejs\npm.CMD
  npmPackages:
    jest: ^30.2.0 => 30.2.0

Contributor guide

Tech stack
typescriptnodejs
Domain
testing
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic Node.jsWindows path concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The error originates in unrs resolver when encountering a Windows volume mount path starting with '\\?\'. Investigate the resolver code, likely in the path normalization or file existence checks, to handle these paths. Look at the linked screenshots for exact error location. Possible fix: detect Windows extended length paths and convert them to a supported format or skip the unsupported construct check. Confirm with maintainers if this is a known limitation.