react-native: The module factory of `jest.mock()` is not allowed to reference any out-of-scope variables.

Downgrading my version of yarn didn’t change anything. However, downgrading my node version from 10 to 8 solved the error.

Not sure why, but you guys really need to take a look at this.

That is related to Node.js version for sure. It started appearing right after upgrading from 9.x to 10.0 and fixed itself when downgraded to 9.x.

Basically you need the latest jest ( 22.4.4 released on today ) to support node 10 for react native.

Having similar issue here after upgrading to node version 10.X

Same case, upgrade from node 9.x to 10.x resulted in error below

FAIL  src/services/Helpers/test.js
 ● Test suite failed to run

   /Users/ilja/Documents/Repositories/skimitar/node_modules/react-native/jest/setup.js: babel-plugin-jest-hoist: The module factory of `jest.mock()` is not allowed to reference any out-of-scope variables.
   Invalid variable access: console
   Whitelisted objects: Array, ArrayBuffer, Boolean, DataView, Date, Error, EvalError, Float32Array, Float64Array, Function, Generator, GeneratorFunction, Infinity, Int16Array, Int32Array, Int8Array, InternalError, Intl, JSON, Map, Math, NaN, Number, Object, Promise, Proxy, RangeError, ReferenceError, Reflect, RegExp, Set, String, Symbol, SyntaxError, TypeError, URIError, Uint16Array, Uint32Array, Uint8Array, Uint8ClampedArray, WeakMap, WeakSet, arguments, expect, jest, require, undefined, DTRACE_NET_SERVER_CONNECTION, DTRACE_NET_STREAM_END, DTRACE_HTTP_SERVER_REQUEST, DTRACE_HTTP_SERVER_RESPONSE, DTRACE_HTTP_CLIENT_REQUEST, DTRACE_HTTP_CLIENT_RESPONSE, global, process, Buffer, clearImmediate, clearInterval, clearTimeout, setImmediate, setInterval, setTimeout.
   Note: This is a precaution to guard against uninitialized mock variables. If it is ensured that the mock is required lazily, variable names prefixed with `mock` are permitted.

@borisyankov Can confirm, all my tests fail on 10.0 but pass on 9.x

Yeah, fixed in 23.0.0: https://github.com/facebook/jest/pull/6075 (It’s in the changelog 😉)

@hramos I’m using node 8.9 with latest react-native (0.56.0-rc.1) and still seeing this error.

The simplest workaround is to patch babel-plugin-jest-hoist as shown below. But if the babel folks don’t like this, then it looks like the correct fix is to use a lowercase ‘m’ in jest/MockNativeMethods.js and make corresponding changes in other files.

--- node_modules/babel-plugin-jest-hoist/build/index.js.orig	2018-06-14 17:36:51.000000000 -0700
+++ node_modules/babel-plugin-jest-hoist/build/index.js	2018-06-14 17:37:09.000000000 -0700
@@ -112,7 +112,7 @@
       if (!found) {
         invariant(
           (scope.hasGlobal(name) && WHITELISTED_IDENTIFIERS[name]) ||
-            /^mock/.test(name) ||
+            /^[Mm]ock/.test(name) ||
             // Allow istanbul's coverage variable to pass.
             /^(?:__)?cov/.test(name),
           'The module factory of `jest.mock()` is not allowed to ' +

From I test, jest is the only problem I run into before they release 22.4.4.

Same problem while running Jest tests on Node v10.1.0 downgrading to 8.x.x fixed the issue

We do not support Node 10.x yet, but this will get resolved at the time of support (which is to happen soon anyway)

For anyone want to use with node 10, update jest in package.json

    "jest": "23.0.0-charlie.1"