Legacy timers should check for presence in global before adding an immediate

[julienw]

Following up #11511:

🐛 Bug Report

With this:

test('foo', () => {
  jest.useFakeTimers('legacy');
  setImmediate(() => {});
});

I get:
=> TypeError: this._timerAPIs.setImmediate is not a function

We're with the jsdom environment.

[lukeapage]

Got this too after upgrading to v27. I'm not sure why. Adding the following to jestSetup stops it happening:

global.setImmediate = global.setTimeout;

more direct references from where it was discussed previously:
#11511 (comment)

#11511 (comment)

[joeldenning]

Still seeing this with jest 27.0.6

[github-actions]

This issue 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.