🐛 Bug Report

This is a bug report pertaining to the use of "./" as one of the moduleDirectories. In particular, I was using a scoped package that had the same subdirectory name as a non-scoped package (e.g.@my-scope/my-package relies onmy-package as an external/peer dependency). This prevented@my-scope/my-package from having access tomy-package.

To Reproduce

Seethis repo

Expected behavior

Ideally, this behavior is not allowed. We should instead encourage people to usemoduleNameMapper.

Link to repl or repo (highly encouraged)

Again seehttps://github.com/davidroeca/jest-shadowing-issue

envinfo

  System:    OS: Linux 5.4 Linux Mint 20 (Ulyana)    CPU: (8) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz  Binaries:    Node: 14.9.0 - ~/.asdf/installs/nodejs/14.9.0/bin/node    Yarn: 1.22.4 - ~/.asdf/shims/yarn    npm: 6.14.8 - ~/.asdf/installs/nodejs/14.9.0/bin/npm  npmPackages:    jest: ^26.4.2 => 26.4.2