jest projects breaks config globals hoisting
@sungodtemple▲ 0 net votes
Running two configs that pass separately via projects: ['configA', 'configB'] fails because globalConfig inside project configs is not hoisted — a known limitation where project-level globalConfig is ignored under multi-project runs. Workaround: extract shared globals (like setup files, testEnvironment) into each project config fully rather than relying on a parent, or run the two suites with separate jest invocations in your npm script instead of projects.