jestjs/jest

Jest should resolve its dependencies from its own location rather than rootDir

Open

#5,913 建立於 2018年4月3日

在 GitHub 查看
 (21 留言) (30 反應) (0 負責人)TypeScript (45,361 star) (6,653 fork)batch import
ConfirmedHelp WantedPinned

描述

Create React App users bumped into this issue recently. A third party package started depending on jest-validate, and that caused npm to hoist jest-environment-node to the top of the app tree. Unfortunately, Jest resolves environment package from the project root instead of from its own Node module location so as a result, it loads the wrong (hoisted) jest-environment-node.

I think the jest package should resolve any own dependencies from its own location (just like Node resolution works) rather than from the project root folder.

貢獻者指南

技術棧
javascripttypescriptnodejs
領域
tooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Node.js module resolutionJest internals
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
Examine the resolution logic in packages/jest config/src/utils.js around lines 109-111. Understand how the environment package is resolved from the project root. Investigate using require.resolve from Jest's own directory (e.g., dirname) to fix hoisting issues. Review the linked CRA issue for additional context. Ensure no breaking changes to other dependency resolutions.
Jest should resolve its dependencies from its own location rather than rootDir · jestjs/jest#5913 | Good First Issue