Unable to run tests

[AlexJWayne]

I cannot get the test that is generated with the empty project to pass.

> nx run foo:test 
 FAIL   foo  apps/foo/App.spec.tsx
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/alexwayne/expo-tests/node_modules/react-native/Libraries/polyfills/error-guard.js:45
    } < mixed > , TOut;
                ^

    SyntaxError: Unexpected token ','

      at Runtime.createScriptFromCode (../../node_modules/jest-runtime/build/index.js:1597:14)
      at Object.<anonymous> (../../node_modules/react-native/jest/setup.js:277:6)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        2.212 s
Ran all test suites.

———————————————————————————————————————————————

>  NX   ERROR  Running target "foo:test" failed

  Failed tasks:
  
  - foo:test
  
  Hint: run the command with --verbose for more details.

I have an example repository here that demonstrates the problem: https://github.com/AlexJWayne/expo-tests
Pull that down and run nx test foo to get the above error.

That error is not the first error I encountered. I made a number of tweaks to get this working. See AlexJWayne/expo-tests@1c7e900...e366a2d

These changes were made according to the documentation for testing Expo.

node v14.17.6 was uses for this demonstration.