add console global to the whitelisted identifiers

[ilyagru]

Summary

This PR adds the console global variable to the whitelisted identifiers.
The issue is mainly with CIs that use this. The issue cannot be seen if you don't have any mocks locally.

● Test suite failed to run

/Users/vagrant/git/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.

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)

Here is the reference to the issue.
#2567

Test plan

No tests for this.

[facebook-github-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[codecov-io]

Codecov Report

Merging #6075 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6075   +/-   ##
=======================================
  Coverage   64.12%   64.12%           
=======================================
  Files         217      217           
  Lines        8332     8332           
  Branches        3        4    +1     
=======================================
  Hits         5343     5343           
  Misses       2988     2988           
  Partials        1        1

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a5e9894...5e22041. Read the comment docs.

[cpojer]

Yap, that makes sense.

[byCedric]

Thanks for merging this, we were having issues related to this. But you guys realise it's not PR#6074 but PR#6075 right? The changelog refers to PR#6074...

[thymikee]

@byCedric mind sending a fix to the changelog? :)

[byCedric]

@thymikee There you go! 😄

[byCedric]

Is a release including this fix scheduled soon?

[SimenB]

Sorry, not scheduled for some time. We're working on Jest 23 at the moment.

You can use jest.doMock for now.

[jtich]

I came across this issue when attempting to run some jest tests on a newly created React Native app... jest.doMock did not work (in my case).

That said, adding the following into the jest section in my package.json did the trick:

"transformIgnorePatterns": [
      "[/\\\\]node_modules[/\\\\].+\\.(js|jsx|mjs)$"
]

[byCedric]

Good one, for me just using an older node version than 10 (I recommend an LTS, like 8) did the trick. I secretly stole it from React Storybook who referenced the issue here 3 days ago.

[zeh]

Is there a way to make this work that doesn't depend on specific Node versions? My tests suddenly stopped working. We're not using jest.mock or jest.doMock anywhere in our own tests' code, so not sure what the approach should be here to fix it for console.

[rickhanlonii]

@zeh try out jest@beta

[zeh]

@rickhanlonii Can confirm that jest@beta works. Thanks!

[redbar0n]

Upgrading babel-jest with yarn add --dev babel-jest babel-core regenerator-runtime fixed this error for me.

[github-actions]

This pull request 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.