-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
updates jest
/ts-jest
to latest
#9155
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Skipped Deployments
|
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected] |
2f13ddd
to
adc2abd
Compare
adc2abd
to
24078b0
Compare
24078b0
to
a5e1d49
Compare
a5e1d49
to
609536c
Compare
609536c
to
1c754ab
Compare
1c754ab
to
2a98608
Compare
6deb211
to
e159ce2
Compare
e159ce2
to
02749b3
Compare
jest
, ts-jest
, and @types/jest
to latestjest
/ts-jest
to latest
@@ -356,9 +356,9 @@ mod test { | |||
use crate::{task_graph::TaskDefinition, turbo_json::CONFIG_FILE}; | |||
|
|||
#[test_case(r"{}", TurboJson::default() ; "empty")] | |||
#[test_case(r#"{ "globalDependencies": ["tsconfig.json", "jest.config.js"] }"#, | |||
#[test_case(r#"{ "globalDependencies": ["tsconfig.json", "jest.config.ts"] }"#, |
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 was unsure about this at first, but it seems to be happy. please double-check.
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.
A few questions but nothing blocking, thanks for tackling this!
Description
Note
there's a lot here, but I tried to make it easier to review by doing a good job of separating the different phases of the PR into their own commits - so for this one you'll probably have a much better review experience if you read commit-by-commit.
I noticed that we were getting lots of errors when running tests due to running an unsupported version of TypeScript (as compared to what our version of
jest
knew about). This is solved by updating our dependencies. Coincidentally, there's a good few reasons to upgrade anyway, so this comes at a good time.Follow-ups after this PR
"lint": "eslint src/"
in 16 packages, which skips the test files. Start linting tests (which, will involve fixing lints in tests).get-turbo-upgrade-command.test.ts
) are timing out on GitHub Actions, and we believe the cause is running out of I/O (which the tests do a lot of). Attempt to fix this by moving to an in-memory filesystem for tests.Testing Instructions
run
pnpm test