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.