fix: revert usage of Escalade and yargs@16 as they breaks Node 13

[SimenB]

Summary

Fixes #10596

This reverts commit 0a9e77d.

Let's land it for Jest 27 instead

Test plan

🤷

[TrySound]

It's not only escalade. Reported comment was about yargs.

[TrySound]

https://unpkg.com/browse/yargs@16.0.3/package.json

[SimenB]

Good call, I'll rollback yargs as well

[TrySound]

node-notifier also depends on uuid 8.3 with es modules support

[TrySound]

get-package-type from @istanbuljs/load-nyc-config has exports field

[SimenB]

Bah. I'll install node 13 and verify

[SimenB]

@istanbuljs/load-nyc-config doesn't matter as it's never invoked (we pass config explicitly).

Rolling node-notifier back to 7.0.1 works (with jest --notify --coverage) on v13.2.0, but reopens #9701. @mikaelbr thoughts on using uuid@7 in latest node-notifier? I know supporting EOL versions of node sucks, so I understand if you don't want to 🙂

[SimenB]

Almost worth a quick Jest 27 after this just reverting this commit and updating engines to exclude v13... Almost.

[mikaelbr]

@SimenB Using uuid would be fine by me, can also add node 13 to test engines. Not able to do it right away, though, as I am on a short vacation without access to a laptop.

[SimenB]

It's specifically old versions of node 13, not the latest ones. Probably not worth it

[SimenB]

That said, we've been installing a version of node-notifier with uuid@8 for months. It's lazy loaded, so it only impacts people who do --notify. We could just keep it at that version since nobody has complained about it? The other 2 deps are always used though, so we should revert those to working versions.

Jest itself will use exports in the next major, so all of this is void at that point anyways.

[SimenB]

I'll keep node-notifier at 8 for now. I think asking people to use a non-EOL release of node if they want notifications working is fine.

[lukeed]

This has been resolved in escalade and yargs

[SimenB]

Ah, great news! I still think we'll wait until Jest 27 regardless (#9921)

[lukeed]

No problem, just letting you know :) Everyone has/had this problem thanks to Node 13.x experiments.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.