Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: sharded test never fail when using Jasmine < 4 #3360

Merged
merged 1 commit into from
Mar 11, 2022

Conversation

alan-agius4
Copy link
Contributor

if (/^3\.[1-9]\.|^2\./.test(jrunner.coreVersion())) {
console.warn(`DEPRECATED: Support for Jasmine versions prior to '3.10.x' is deprecated in '@bazel/jasmine'.`);
// Jasmine versions prior to 4.0.0 should use the old API.
if (jrunner.coreVersion().charAt(0) !== '4') {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not: what happens when they release 5.0?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use a peerDep as an additional warning at install time?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When version 5 is release, the new API will be used. Currently the peer dependencies are too permissive

https://github.com/bazelbuild/rules_nodejs/blob/8606c50dcf030efaa5cf15c06b7f92e787a8f292/packages/jasmine/package.json#L30-L31

Maybe we should change them to:

>=2.99.0 <5

If we change however the peerDeps to ^4.0.0, this can be considered as a breaking chance since with NPM 7 this will cause the installation to fail when there are unmatched peer deps

@alexeagle alexeagle merged commit add1452 into bazel-contrib:stable Mar 11, 2022
@alan-agius4 alan-agius4 deleted the sharded-test-3 branch March 11, 2022 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants