Make tests pass using Node 5 / NPM 3

[steveluscher]

Right now, if you npm install using Node >=5 and NPM >=3 you'll run into a bunch of problems.

Most of these are due to the fact that npm installs dependencies in a flat directory structure, which makes the paths in unmockedModulePathPatterns (see package.json) no longer match.

Another problem is that the paths in our .flowconfig files may no longer match.

There are undoubtedly other problems.

The task is to make npm test pass all-green with both NPM 2 & 3, or make it pass exclusively with NPM 3 and update the engines config in package.json if dual-compatibility is too much of a pain.

[raineroviir]

I'll give this a try

[raineroviir]

I removed the nesting node_modules in unmockedModulePathPatterns and I'm at
75 tests failed, 1092 tests passed (1167 total in 96 test suites, run time 62.275s)

[steveluscher]

Related: jestjs/jest#554

[raineroviir]

Okay so based on that issue and also related: facebook/react#5183, the issue is with jest and to solve it you unmock all the deps, except for 3 packages that are needed to pass the tests.
I set the package.json to look like:

"unmockedModulePathPatterns": [
      "<rootDir>/node_modules/(?!(fbjs/lib/ErrorUtils.js$|fbjs/lib/fetch.js$|fbjs/lib/fetchWithRetries.js$))"
    ]

1167 tests passed (1167 total in 96 test suites, run time 60.464s) 🎉

[cpojer]

I'll publish a new version of jest-cli@next today that should resolve the npm3 mocking issues.

[kassens]

We've been running node 5 for a while on travis by now.