ts-jest detect @babel/core automatically before detecting babel-core, so if I use some package that uses @babel/core internally, I cannot use babel-core.
I can use babel-core if I want.
# content of debug.txt :
@Ailrun you can test our latest beta (see #697) which will use the babel-core first and then @babel/core. Then you install or not the [email protected] to use the 7 or not, just as other babel related packages.
@huafu I tested with both versions, and both work well. Thanks.
However, coverage does not work with babel@7... I will make another issue for this.
@Ailrun you meant, with ts-jest beta + babel7, coverage do not work?
In ts-jest@next, @babel/core@7, and babel-jest@23.6. I'm trying to reproduce it with minimal repo.
Thanks a lot @Ailrun. I'm actually adding an e2e test in beta for coverages, just realized there was none!
_BTW, we now have a Slack channel_
I think I also could close this.
@Ailrun we left this one open as the current release does not fix the issue, only beta ;-)
Update: when beta will be merged to master and published on the latest and not next npm tag, then we'll close this issue. Other issues, prefixed with [beta], are only related to beta and can be closed as soon as a new beta is released