[Feature]: Allow `globalSetup` to access things in `globals`

🚀 Feature Proposal

Include globals in global config so that globalSetup or globalTeardown can use it.

Motivation

I notice that Jest has globals, but it isn’t included in global config. When I look at name globals, I was thinking about it would be included in global config. So it would match with things related to “global”.

I have a use case https://github.com/thymikee/jest-preset-angular/issues/1348 which if Jest allows globals to be in global config, it will look beautiful.

Example

Define in Jest config

// jest.config.js
//...
globals: {
      'ngcc': { project: 'tsconfig.spec.json' },
}

In a globalSetup script

import type { Config } from '@jest/types';

export = async (globalConfig: Config.GlobalConfig) => {
      console.log(globalConfig.globals);
}

Pitch

This would be a change in Jest config. I think it should be in core.

[SimenB]

Yeah, that’s what I meant in https://github.com/facebook/jest/issues/12436#issuecomment-1046203834

[github-actions[bot]]

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.