Jest-resolve does not resolve dependencies correctly

[nickpape]

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

By default, when Node.js loads a module from a path that is symbolically linked to a different on-disk location, Node.js will dereference the link and use the actual on-disk "real path" of the module as both an identifier and as a root path to locate other dependency modules. In most cases, this default behavior is acceptable. However, when using symbolically linked peer dependencies, as illustrated in the example below, the default behavior causes an exception to be thrown if moduleA attempts to require moduleB as a peer dependency:

Jest-resolve does not do this, it acts as if the --preserve-symlinks flag was always on.

What is the expected behavior?

Jest-resolve should not preserve symlinks unless the flag is present.

[tipng]

Related to #5852 ?

[SimenB]

@nickpape-msft this is closed by #5085, isn't it?

[octogonz]

Yes, we can close this issue. It was fixed in Jest 22.4.3.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.