Cannot find module 'setupDevtools' from 'setup.js' - Platform Windows

[meinto]

Do you want to request a feature or report a bug?

bug

What is the current behavior?

When i run the tests on a linux maschine everything is fine. When i run the tests with the same configuration on my windows computer the following error is thrown:

Cannot find module 'setupDevtools' from 'setup.js'

Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.

OS - Windows

package.json

{
  ...
  "dependencies": {
    "react": "16.0.0-alpha.12",
    "react-native": "0.45.1",
    "react-native-mirror": "0.0.19"
  },
  "devDependencies": {
    "babel-jest": "20.0.3",
    "babel-preset-react-native": "1.9.2",
    "cross-env": "^5.0.0",
    "jasmine-reporters": "2.2.1",
    "jest-cli": "20.0.4",
    "react-native-cli": "^2.0.1",
    "react-test-renderer": "16.0.0-alpha.13"
  },
  "jest": {
    "collectCoverage": true,
    "setupTestFrameworkScriptFile": "./setup-jasmine-env.js",
    "preset": "react-native"
  }
}

setup-jasmine-env.js

var jasmineReporters = require('jasmine-reporters')
jasmine.VERBOSE = true

.babelrc

{
  "presets": [
    "react-native"
  ],
  "retainLines": true,
  "sourceMaps": true
}

Many thanks for helping!

[tuanmai]

@tobiasMeinhardt Hey, we encountered the same issue with you. Our solution is
rm yarn.lock && rm -rf node_modules && yarn. Seems that there is a problem with the yarn.lock file

[cpojer]

I think that was some dependency that I published either for Jest or Metro that was messed up, now it should be resolved.

[blackxored]

I'm having the same issue:

yarn list v0.24.6
├─ jest@20.0.4
├─ react-native@0.45.1
└─ react@16.0.0-alpha.12
✨  Done in 1.00s.

Did clean node_modules and yarn.lock.

[brobiden]

Still having this issue as well

[meinto]

Unfortunately i still have this issue. I removed yarn.lock, removed the folder node_modules and installed the modules again.

npm run test still throws the same error:

 Test suite failed to run

    Cannot find module 'setupDevtools' from 'setup.js'
      
      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:179:17)
      at Object.<anonymous> (node_modules/react-native/jest/setup.js:30:1)

The test command in my package.json looks like follows:

{
  "scripts": {
     "test": "cross-env NODE_ENV=test jest --silent --collectCoverageFrom='[\"src/**/*.{js}\"]'"
  }
}

@cpojer - you said maybe a dependency for jest was messed up. Do i have to install/update a package? The latest version of jest-cli is still 20.0.4.

[khanghoang]

@tobiasMeinhardt can you create a fresh RN project and try to run jest on it. I know it's weird but let try it, if it works then maybe you need to clean your project.
In my case, I need to clean everything to make it work again.

[meinto]

Thanks for all the help!

My project is a library with an Examples folder. This was the problem. In this example folder i have multiple example projects with - of course - a node_modules folder in each of it.

To solve my problem i added modulePathIgnorePatterns to my jest configuration of my root library project.

package.json of my library project:

{
  "jest": {
    "modulePathIgnorePatterns": ["<rootDir>/Examples/"],
  }
}

After that i ran npm test -- --no-cache. This solved it for me.

[zheng-liu-seattle]

i am also having this issue, on mac, tried to clean node_modules, but still see it.

[phillbaker]

Was seeing a similar issue on our CI runs:

Test suite failed to run

    Cannot find module 'setupDevtools' from 'setup.js'
      
      at Resolver.resolveModule (../../../../../<root>/node_modules/jest-resolve/build/index.js:169:17)
      at Object.<anonymous> (node_modules/react-native/jest/setup.js:23:1)

root issue for us was that ./node_modules was symlinked to another node_modules elsewhere.

[ancyrweb]

Running npm test -- --no-cache made it for me

[peterleilei86]

Having the same issue!
OS: Mac OS,
jest config:

"jest": {
    "preset": "react-native",
    "transform": {
      "^.+\\.js$": "<rootDir>/node_modules/babel-jest",
      ".(ts|tsx)": "<rootDir>/node_modules/ts-jest/preprocessor.js",
      "\\.(jpg|jpeg|png|gif|eot|otf|webp|svg|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga)$": "<rootDir>/fileTransformer.js"
    },
    "testRegex": "(/__tests__/.*|\\.(test|spec))\\.(ts|tsx|js)$",
    "moduleFileExtensions": [
      "ts",
      "tsx",
      "js"
    ],
    "moduleNameMapper": {
      "\\.(css|less)$": "identity-obj-proxy",
      "^React$": "<rootDir>/node_modules/react"
    },
    "modulePathIgnorePatterns": [
      "<rootDir>/node_modules/react-native/Libraries/"
    ],
    "verbose": true
  }

package.js:

"dependencies": {
    ......
   "react": "16.0.0-alpha.13",
   "react-dom": "16.0.0-alpha.13",
   "react-native": "0.45.1"
},
"devDependencies": {
    "@types/jest": "^20.0.2",
    "babel-cli": "^6.2.0",
    "babel-core": "^6.10.4",
    "babel-jest": "^20.0.3",
    "babel-preset-react-native": "^1.9.2",
    "jest": "^20.0.4",
    "jest-cli": "^20.0.4",
    "react-test-renderer": "^15.6.1",
    "regenerator-runtime": "^0.10.5",
    "ts-jest": "^20.0.6",
     #......
}

[peterleilei86]

@phillbaker Hey I am having the same issue. Can you elaborate the root issue on your case and the solution? Thanks so much

[phillbaker]

@peterdev6 we were seeing this issue only on our CI, where we "cache" our node_modules and then before running npm test we would ln the ./node_modules to that cached directory. My guess is that there's a hardcoded path to load setupDevtools, or something similar, which doesn't like the symbolic link. In our case, switching to just mving or cping the cached directory to a local reference worked.

Hope it helps.