jestjs/jest

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

Open

#5,913 opened on 2018年4月3日

GitHub で見る
 (21 comments) (30 reactions) (0 assignees)TypeScript (6,653 forks)batch import
ConfirmedHelp WantedPinned

Repository metrics

Stars
 (45,361 stars)
PR merge metrics
 (平均マージ 11d 22h) (30d で 11 merged PRs)

説明

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.

コントリビューターガイド