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: update min ts version of jest
& co to 3.8 to allow bumping dependencies
#48473
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,7 +3,7 @@ | |
// Definitions by: Pete Gonzalez <https://github.com/octogonz> | ||
// Ian Clanton-Thuon <https://github.com/iclanton> | ||
// Definitions: https://github.com/DefinitelyTyped/DefinitelyTyped | ||
// TypeScript Version: 3.5 | ||
// TypeScript Version: 3.8 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Heft currently ships with Jest 25. Seems like this change should wait until Heft upgrades its Jest dependency. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Any idea of when that might be? I don't think this'll be a problem so long as Heft can support TypeScript 3.8, which by the looks of it it can. |
||
|
||
/// <reference types="jest" /> | ||
/// <reference path="./mocked.d.ts" /> | ||
|
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -28,6 +28,7 @@ | |||||
// Pawel Fajfer <https://github.com/pawfa> | ||||||
// Regev Brody <https://github.com/regevbr> | ||||||
// Definitions: https://github.com/DefinitelyTyped/DefinitelyTyped | ||||||
// Minimum TypeScript Version: 3.8 | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For the sake of consistency, this should be:
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See, I'd prefer that for consistency, but the readme says it should have that word 🤔 |
||||||
|
||||||
declare var beforeAll: jest.Lifecycle; | ||||||
declare var beforeEach: jest.Lifecycle; | ||||||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
{ | ||
"private": true, | ||
"dependencies": { | ||
"jest-diff": "^25.2.1", | ||
"pretty-format": "^25.2.1" | ||
"jest-diff": "^26.0.0", | ||
"pretty-format": "^26.0.0" | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't actually think this is needed - I can't find any evidence of
@types/jest
being used in this file, but will look into it further once I've got CI green.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that the original reference was to
jasmine
, and was because it was argumenting the globaljasmine
namespace.However, while v2 of
@types/frisby
removed this argumenting, the reference was kept in because the author wanted to have@types/jasmine
pulled in because the library usedjasmine
?I can understand why, and am not against it, but I think it would be better to remove this reference since
frisby.js
doesn't listjest
as a dependency (not even as apeerDependency
) nor does it require/import it anywhere, and because people using TypeScript will need to install@types/jest
anyway as they'll be consuming them directly.Additionally, the source code of
frisby
still referencesjasmine
rather thanjest
, and was originally switched tojest
as thejasmine
types were causing problems (#32191).@cwoodland @johnny4753 thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made #48935 to remove the reference.