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
When running jest in a package that has both a custom transform module and a dependency that has been linked in using yarn link, jest fails to load the transformer. If the transform module is installed in the repository that is linked, the problem disappears.
There were a couple of reports of this problem in kulshekhar/ts-jest#424, but it appears the problem is with jest.
This seems related to #5085, but the test case reproduces with jest 23.0.0-alpha.1, which I think includes that PR already, so I think this is a different issue.
The text was updated successfully, but these errors were encountered:
felipeochoa
changed the title
Custom transfer fails to import when yarn-linking unrelated child
Custom transformer fails to import when yarn-linking unrelated child
Mar 21, 2018
This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.
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.
This is a bug report.
When running
jest
in a package that has both a customtransform
module and a dependency that has been linked in usingyarn link
, jest fails to load the transformer. If the transform module is installed in the repository that is linked, the problem disappears.There were a couple of reports of this problem in kulshekhar/ts-jest#424, but it appears the problem is with jest.
This seems related to #5085, but the test case reproduces with jest 23.0.0-alpha.1, which I think includes that PR already, so I think this is a different issue.
I've created a small reproduction repo here.
The text was updated successfully, but these errors were encountered: