Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support jest@test version

See original GitHub issue

Issue

It would be cool if you upgrade your Jest peerDependency to the latest test version of Jest. At the moment I’m getting "ts-jest#jest@^20.0.0" doesn't satisfy found match of "jest@20.1.0-delta.4"

The reason for trying out the latest delta version is this issue https://github.com/facebook/jest/pull/4088 that I am encountering all the time.

Thanks ☺️

Issue Analytics

State:
Created 6 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

gdbortoncommented, Aug 29, 2017

@kulshekhar You can test the semver values here - https://semver.npmjs.com/

"^20.0.0 || > 21.0.0-alpha || > 20.1.0-alpha" matches everything in 20.x, 20.1 prereleases, and current 21.0 prereleases.

Sadly npm doesn’t seem to have a simple way of saying match > 20.x.x-alpha.

0reactions

pelotomcommented, Aug 29, 2017

From here,

If a version has a prerelease tag (for example, 1.2.3-alpha.3) then it will only be allowed to satisfy comparator sets if at least one comparator with the same [major, minor, patch] tuple also has a prerelease tag.

The current jest@test is up to v21.0.0-beta.1, so I think we need to use a version range of