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

jmkitavi · 2018-05-03T22:10:15Z

I have reviewed the documentation
I have searched existing issues
I am using the latest React Native version

Environment

My Environment is as below.

Scanning folders for symlinks in /Users/sirjmkitavi/Andela/playground/react-native/ball-animation/node_modules (25ms)

Environment:
  OS: macOS High Sierra 10.13.2
  Node: 10.0.0
  Yarn: 1.6.0
  npm: 5.6.0
  Watchman: 4.9.0
  Xcode: Xcode 9.2 Build version 9C40b
  Android Studio: Not Found

Packages: (wanted => installed)
  react: ^16.3.2 => 16.3.2
  react-native: ^0.55.3 => 0.55.3

Steps to Reproduce

Initialise react-native application. Preferably using react-native-clie

i.e react-native init SampleProj
Ensure you have atleast one test.
Run yarn test

Expected Behavior

The expected behaviour is for the tests to run successfully. To either fail or pass.

Actual Behavior

All test suites fail throwing the error below

 /Users/{user}/pulse/pulse-mobile-app/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
...

The error message continues to say

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.

      at invariant (node_modules/babel-plugin-jest-hoist/build/index.js:14:11)
      at newFn (node_modules/babel-traverse/lib/visitors.js:276:21)
      at NodePath._call (node_modules/babel-traverse/lib/path/context.js:76:18)
      at NodePath.call (node_modules/babel-traverse/lib/path/context.js:48:17)
      at NodePath.visit (node_modules/babel-traverse/lib/path/context.js:105:12)
      at TraversalContext.visitQueue (node_modules/babel-traverse/lib/context.js:150:16)

The text was updated successfully, but these errors were encountered:

jmkitavi · 2018-05-04T09:11:11Z

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.

tomaskazatel · 2018-05-04T15:34:58Z

👍 /home/circleci/repo/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.. I cant build RN app on CircleCI.

Full Error log

/home/circleci/repo/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, 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.
      
      at invariant (node_modules/babel-plugin-jest-hoist/build/index.js:14:11)
      at newFn (node_modules/babel-traverse/lib/visitors.js:276:21)
      at NodePath._call (node_modules/babel-traverse/lib/path/context.js:76:18)
      at NodePath.call (node_modules/babel-traverse/lib/path/context.js:48:17)
      at NodePath.visit (node_modules/babel-traverse/lib/path/context.js:105:12)
      at TraversalContext.visitQueue (node_modules/babel-traverse/lib/context.js:150:16)

borisyankov · 2018-05-07T09:47:46Z

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.

DaveVanVliet · 2018-05-07T14:29:12Z

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

xzilja · 2018-05-10T12:42:58Z

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.

patlub · 2018-05-11T12:18:42Z

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

codeithuman · 2018-05-15T21:31:37Z

Same issue with Node v10.1.0. Downgraded to Node v8.11.1 via homebrew and tests are passing again.

gengjiawen · 2018-05-16T00:25:59Z

Maybe it's a problem with jest, I tried to report it to jest when I have time.

gengjiawen · 2018-05-16T02:48:54Z

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

    "jest": "23.0.0-charlie.1"

gengjiawen · 2018-05-16T02:53:31Z

I have reported to jest in jestjs/jest#6196. If you want to fix this asap, please upvote that issue.

carloscuesta · 2018-05-16T08:36:14Z

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

gengjiawen · 2018-05-18T13:18:36Z

@hramos Jest has released a new version, I think we can close this.

gengjiawen · 2018-05-18T13:50:30Z

@grabbou Do you think a new release is needed or put this in change log ?

gengjiawen · 2018-05-18T13:51:23Z

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

grabbou · 2018-05-20T21:59:53Z

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

gengjiawen · 2018-05-21T02:07:47Z

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

douglowder · 2018-06-15T00:43:02Z

@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 ' +

hramos · 2018-06-15T17:02:53Z

^ @pvdz

gengjiawen · 2018-06-16T00:35:04Z

@dlowder-salesforce Can you try latest nodejs 8 and jest ?

mjesun · 2018-06-18T15:07:17Z

cc / @SimenB, @thymikee, do you recall if we had a fix for this? I think I've recently seen something about whitelisting console.

SimenB · 2018-06-18T15:58:59Z

Yeah, fixed in 23.0.0: jestjs/jest#6075 (It's in the changelog 😉)

timwangdev · 2018-06-20T07:17:24Z

    babel-plugin-jest-hoist: The module factory of `jest.mock()` is not allowed to reference any out-of-scope variables.
    Invalid variable access: MockNativeMethods

My error is about MockNativeMethods

thymikee · 2018-06-20T07:25:55Z

@mjesun @SimenB console was fixed, but the mock* variables being whitelisted too could be updated on Jest side to also honor uppercase Mock*. I don't see a reason why not to allow it.

Rolando-Barbella · 2018-07-12T20:21:30Z

I'm using react-native with expo and just did:

"jest-expo": "28.0.0"

node 10.6.0

andyrichardson mentioned this issue May 10, 2018

Tests fail when using node:latest docker image andyrichardson/project-cycle#1

Closed

react-native-bot added the JavaScript label May 11, 2018

hramos mentioned this issue May 11, 2018

[Node 10] Prepare for Node 10 #19229

Closed

2 tasks

gengjiawen mentioned this issue May 16, 2018

Draft a new stable release to fix react native on node 10 jestjs/jest#6196

Closed

gengjiawen mentioned this issue May 16, 2018

add test case for https://github.com/facebook/jest/pull/6075 jestjs/jest#6198

Closed

hramos closed this as completed May 24, 2018

douglowder reopened this Jun 15, 2018

thymikee mentioned this issue Jun 20, 2018

Add Mock* prefixed variables to be whitelisted by babel-plugin-jest-hoist jestjs/jest#6504

Closed

timwangdev mentioned this issue Jun 20, 2018

[babel-plugin-jest-hoist] Fix MockNativeMethods access in react-native jestjs/jest#6505

Merged

cpojer closed this as completed in jestjs/jest#6505 Jun 20, 2018

facebook locked as resolved and limited conversation to collaborators Jul 16, 2018

react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jun 20, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

jmkitavi commented May 3, 2018 •

edited

Loading

jmkitavi commented May 4, 2018

tomaskazatel commented May 4, 2018 •

edited

Loading

borisyankov commented May 7, 2018 •

edited

Loading

DaveVanVliet commented May 7, 2018

xzilja commented May 10, 2018

patlub commented May 11, 2018

codeithuman commented May 15, 2018

gengjiawen commented May 16, 2018

gengjiawen commented May 16, 2018

gengjiawen commented May 16, 2018

carloscuesta commented May 16, 2018 •

edited

Loading

gengjiawen commented May 18, 2018

gengjiawen commented May 18, 2018

gengjiawen commented May 18, 2018

grabbou commented May 20, 2018

gengjiawen commented May 21, 2018

douglowder commented Jun 15, 2018

hramos commented Jun 15, 2018

gengjiawen commented Jun 16, 2018

mjesun commented Jun 18, 2018

SimenB commented Jun 18, 2018 •

edited

Loading

timwangdev commented Jun 20, 2018

thymikee commented Jun 20, 2018

Rolando-Barbella commented Jul 12, 2018

The module factory of jest.mock() is not allowed to reference any out-of-scope variables. #19120

The module factory of jest.mock() is not allowed to reference any out-of-scope variables. #19120

Comments

jmkitavi commented May 3, 2018 • edited Loading

Environment

Steps to Reproduce

Expected Behavior

Actual Behavior

jmkitavi commented May 4, 2018

tomaskazatel commented May 4, 2018 • edited Loading

borisyankov commented May 7, 2018 • edited Loading

DaveVanVliet commented May 7, 2018

xzilja commented May 10, 2018

patlub commented May 11, 2018

codeithuman commented May 15, 2018

gengjiawen commented May 16, 2018

gengjiawen commented May 16, 2018

gengjiawen commented May 16, 2018

carloscuesta commented May 16, 2018 • edited Loading

gengjiawen commented May 18, 2018

gengjiawen commented May 18, 2018

gengjiawen commented May 18, 2018

grabbou commented May 20, 2018

gengjiawen commented May 21, 2018

douglowder commented Jun 15, 2018

hramos commented Jun 15, 2018

gengjiawen commented Jun 16, 2018

mjesun commented Jun 18, 2018

SimenB commented Jun 18, 2018 • edited Loading

timwangdev commented Jun 20, 2018

thymikee commented Jun 20, 2018

Rolando-Barbella commented Jul 12, 2018

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

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

jmkitavi commented May 3, 2018 •

edited

Loading

tomaskazatel commented May 4, 2018 •

edited

Loading

borisyankov commented May 7, 2018 •

edited

Loading

carloscuesta commented May 16, 2018 •

edited

Loading

SimenB commented Jun 18, 2018 •

edited

Loading