Follow Enzyme's solution to version pinning

Issue :

It’s documented in the readme that ts-jest doesn’t support semver and instead has locked it’s major version to the major version of jest. Overall I can understand the idea here but this does make usage of automated tools such as Renovate and Dependabot a bit harder considering ts-jest has to have custom configuration so it doesn’t follow semver.

Expected behavior :

My suggestion is to follow in the footsteps of enzyme-adapters which suffix the version they work with at the end of the package name (see https://github.com/airbnb/enzyme/tree/master/packages). To replicate that same idea with this repository, when jest@25.0.0 releases, there would be a new package published to npm, ts-jest-25. I will admit it does require a bit more overhead which I can understand if you don’t want to take it on but I figured I would suggest it seeing the parallels between the two projects.

[kulshekhar]

I’ve given this some thought. If this discussion was before the project was started, it’d definitely be a lot more attractive but I really don’t see any benefit in changing the version mechanism because it introduces another unknown without substantial benefit.

[ahnpnl]

@k2snowman69 would be nice if you can help us to implement your proposal.