You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few of our test examples use the tests from other examples and the simplest way to make sure that everything is installed properly is to preserve symlinks, however there doesn't seem to currently be support for preserving sym links with jest.
We are working on developing a work around until this issue can be resolved in jest, though it's unclear if or when that will happen. Here are some PRs and issues pertaining to the subject.
A few of our test examples use the tests from other examples and the simplest way to make sure that everything is installed properly is to preserve symlinks, however there doesn't seem to currently be support for preserving sym links with jest.
We are working on developing a work around until this issue can be resolved in jest, though it's unclear if or when that will happen. Here are some PRs and issues pertaining to the subject.
kulshekhar/ts-jest#825
jestjs/jest#9976
jestjs/jest#7364
jestjs/jest#5356
We tried using a work around like in this gist (which I guess would be a jest gist) (and there was a similar one in jestjs/jest#5356)
https://gist.github.com/gcangussu/af52da296aef829eba15ea626453f031
but the resolver was unable to figure out es modules and we didn't want to invest the resources at this exact moment into figuring that out.
"allowSyntheticDefaultImports": true
to the affected tsconfigs as soon as this is resolvedlinkAndInstallPatch
call"allowSyntheticDefaultImports": true
to the build options in compile_typescript_codeThe text was updated successfully, but these errors were encountered: