From c67ca8576d7fe35621b2dafeb22b1dbf23525db9 Mon Sep 17 00:00:00 2001 From: Asuka Wang Date: Thu, 18 Jul 2024 16:36:09 +0900 Subject: [PATCH] fix(shared): process.env is undefined on non-node runtime issue (#93) * fix: process.env.JEST_WORKER_ID is undefined issue Add null check to `process.env.JEST_WORKER_ID`, and access `process` from `globalThis` to support non-node runtime. * Update findPackageJSON.ts --------- Co-authored-by: Oleksandr Fediashov --- packages/shared/src/findPackageJSON.ts | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/packages/shared/src/findPackageJSON.ts b/packages/shared/src/findPackageJSON.ts index 567444a6..f2107953 100644 --- a/packages/shared/src/findPackageJSON.ts +++ b/packages/shared/src/findPackageJSON.ts @@ -1,6 +1,4 @@ import { dirname, isAbsolute } from 'path'; -import * as process from 'process'; - import findUp from 'find-up'; const cache = new Map(); @@ -10,7 +8,7 @@ export function findPackageJSON( filename: string | null | undefined ) { // Jest's resolver does not work properly with `moduleNameMapper` when `paths` are defined - const isJest = Boolean(process.env.JEST_WORKER_ID); + const isJest = Boolean(globalThis.process?.env?.JEST_WORKER_ID); const skipPathsOptions = isJest && !pkgName.startsWith('.'); try {