Opened this issue here since I didn't find you on Twitter @kulshekhar :)
As per Christoph Pojer, they'll be happy to assist and review PR to make ts-jest be officially part of Jest: https://twitter.com/cpojer/status/874292905589997568
馃帀 馃帀
Could be a good idea to talk about steps for the process
yeah, I'm not active on any social network really :)
That was the original plan when I started work on ts-jest. I did have a bit of a conversation with @cpojer about this (I think he even had an npm package name reserved for it :smile:). The sticking point, iirc, was that ts-jest is a bit of a hack and would only work with V8. This bit hasn't changed. Once things had settled down & ts-jest matured a bit, I did try to see if this could be officially part of Jest. That conversation didn't really take off.
If there's a willingness to take this under Jest, I'm all for it. It can only be helpful for all users.
We can use this thread to take this forward. What would be most helpful, is a set of technical guidelines/requirements from the folks at Jest that can kick-off and guide this process.
Would also to help out. I think a typescript preset in jest would be wonderful for everyone
I think including this in jest directly would make a lot more typescript users comfortable using jest so it would be good for both projects AND users.
@cpojer should we just let this idea die?
No, I'm very much interested in finding a solution for this, albeit I only work on Jest in my free time, so I have limited time to help out.
That's fair enough. Could you perhaps outline a way forward for this (or get someone else to?)