ts-jest can't import jest-config if the node_modules directory isn't flattened

[iclanton]

Issue :

ts-jest seems to assume that consumers are using npm or yarn, which both flatten the node_modules folder and allow packages to import dependencies that are not declared in their package.json. The flattened node_modules folder assumption doesn't hold true for other package managers like pnpm and yarn's plug-and-play feature.

Expected behavior :

ts-jest should be able to resolve jest-config even if the node_modules directory doesn't have flattened dependencies.

Fix

Here's the fix: #853

[ahnpnl]

One thing I forgot to mention, #853 didn't update changelog :)

[iclanton]

It looks like the CHANGELOG.md is only updated when the package is released. Is there an intermediate place where changelog entries are supposed to go before releases?

[ahnpnl]

Hmm I think you are right. It is automatically done once the package is published. Sorry for the inconvenience 👍

[iclanton]

Do you know when the package will be published? It'd be great to start consuming this fix.

[ahnpnl]

Cc @kulshekhar . I don't know when but kul will take care of it :)

[kulshekhar]

I'll try to get this done over the weekend

[iclanton]

Thanks!

[kulshekhar]

This has been published