travis build fails after eject - path to polyfills is broken

[razvanilin]

The builds were successful before the eject command, but now they are not passing and I get this error:

> [email protected] test /home/travis/build/razvanilin/depomo/client
> node scripts/test.js --env=jsdom
 FAIL  src/containers/App.test.js
  ● Test suite failed to run
    ENOENT: no such file or directory, stat '/home/travis/build/razvanilin/depomo/client/\config\polyfills.js'
      
      at Object.fs.statSync (fs.js:907:18)
      at Object.statSync (node_modules/graceful-fs/polyfills.js:297:22)
      at process._tickCallback (internal/process/next_tick.js:103:7)
Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.62s
Ran all test suites.
npm ERR! Test failed.  See above for more details.

The path to polyfills.js seems to be broken. My guess is that I build this app on windows environment and travis uses unix type OSes. My knowledge in how travis works are quite limited and I might be missing something really basic.

I also tried to find where the path is being used in the settings files but couldn't find anything on this matter.

Can somebody shine a light on this?

npm: 3.10.9
Windows 10

travis settings:

language: node_js
node_js:
  - "7"
cache:
  directories:
    - server/node_modules
    - client/node_modules
services: mongodb
script: cd server && npm install && npm test && cd ../client && npm install && npm test

[gaearon]

I think the issue is that if you run eject on Windows, then it hardcodes Windows paths separators into package.json Jest config. You can fix locally by changing the separators in package.json.

The issue itself is tracked in #1498. You can help by submitting a PR fixing it.