Fix end-to-end test to use packages from master

[gaearon]

As noted in #696 (comment), we should have end-to-end test use the versions of packages from the repo instead of ones from npm. We might need to run lerna bootstrap in it or something.

[fson]

It's weird that it only fails in Node v4.5.0, not in 6. We already run lerna bootstrap in the npm postinstall script so that should work.

I also tried running locally on a fresh Node v4.5.0 installation and npm install worked without any errors about peer dependencies.

[fson]

I see what the problem is now, we run npm install again in the react-scripts package after copying it to a clean directory without node_modules. At that point the packages are not bootstrapped, so it installs all the packages from npm.

I think the release script possibly needs to be changed too, because it uses the same strategy when it bundles the dependencies. Unless we publish all the other packages first, the script will bundle the eslint-config-react-app from npm. Perhaps we could make this easier by publishing everything with lerna publish and moving the special handling for react-scrips to a prepublish script, so that it will (hopefully) run after the version numbers have been updated?

[fson]

The e2e test should be fixed here: #699.

[gaearon]

Thanks!

[gaearon]

#723 (comment)