chore(deps): update jest monorepo and ts-jest to v27 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@jest/types	^26.6.2 -> ^27.0.0
jest (source)	^26.2.2 -> ^27.0.0

---

Release Notes

facebook/jest

v27.0.1

Compare Source

Fixes

• [jest-environment-jsdom] Bump version of JSDOM to avoid deprecated request package (#​11442)

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[wolfy1339]

Requires update to ts-jest

[gr2m]

yeah bump to ts-jest@next, I'm doing that for all the other PRs right now. renovate will send us a PR once ts-jest 27 stable will be released

[gr2m]

ts-jest 27.0.0 has now been released

ts-jest has been updated

[gr2m]

The "express middleware no mount path no next" test is currently failing for me in test/integration/node-middleware.test.ts. But when I run it in isolation it works

npx jest -t "express middleware no mount path no next" test/integration/node-middleware.test.ts

I'm not sure what the problem here is. @wolfy1339 any idea what it could be?

[wolfy1339]

The "express middleware no mount path no next" test is currently failing for me in test/integration/node-middleware.test.ts. But when I run it in isolation it works

npx jest -t "express middleware no mount path no next" test/integration/node-middleware.test.ts

I'm not sure what the problem here is. >@wolfy1339 any idea what it could be?

I had the same problem in my PR #552
The only solution I had found was to put the Webhooks middleware last after any other express middleware.

[gr2m]

The only solution I had found was to put the Webhooks middleware last before any other express middleware.

I've read something in the release notes that the running order might change with v27, so that is probably what we see here.

I think we have to figure this out for good now :D

[wolfy1339]

@G-Rath @oscard0m Would you like to assist in debugging this?

[oscard0m]

@G-Rath @oscard0m Would you like to assist in debugging this?

Hi @wolfy1339. I'm sorry but these days I have a limited amount of time to check into this. Just to get context and catch up with Octokit status, how critical is this upgrade? Is it blocking ESModules migration?

[wolfy1339]

Hi @wolfy1339. I'm sorry but these days I have a limited amount of time to check into this. Just to get context and catch up with Octokit status, how critical is this upgrade? Is it blocking ESModules migration?

Native ESM was introduced in this Jest version, so I think it is a critical piece to the migration

[G-Rath]

Likewise I've had a bit of an explosion in work (which is why I've not been able to help out as much lately 😞).

In saying that...

This is because you're calling jest.useFakeTimers, which is a global operation within the file - if you add a jest.useRealTimers call at the start of the test that's failing, it'll start passing :)

Ideally you should add that to all of the tests in the file to ensure the right type of timers (real or fake) are used for each test.

[oscard0m]

Likewise I've had a bit of an explosion in work (which is why I've not been able to help out as much lately 😞).

No worries @G-Rath, I hope everything gets stable soon. 💪🏽
Lots of positive energy to Software Gods.

In my case I lost my job due to COVID situation and now I'm focusing in learning React, building my profile, etc. As soon as I solve my professional situacion I will get back. I'm willing to catch up with all the things you have built lately.

In saying that...

This is because you're calling jest.useFakeTimers, which is a global operation within the file - if you add a jest.useRealTimers call at the start of the test that's failing, it'll start passing :)

Ideally you should add that to all of the tests in the file to ensure the right type of timers (real or fake) are used for each test.

EDIT: Checking out and trying this!
Added jest.useRealTimers() inside an afterEach so it is easier for future unit tests.

NICE CATCH @G-Rath
�

[gr2m]

Great work y’all, thank you!

[github-actions]

🎉 This PR is included in version 9.7.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀