Build errors are not printed to console due to broken require

[svicalifornia]

Is this a bug report?

Yes

Can you also reproduce the problem with npm 4.x?

Yes.

The Problem

Build errors do not print to console to due to an fatal error introduced in PR #2650.

PR #2650 added a new file printBuildError.js, which requires lodash/get. However, lodash is not listed as a dependency in react-script's package.json, so any execution path that requires printBuildError.js will fail to require 'lodash/get', causing node to throw a fatal exception.

Proposed Resolution

'lodash' or 'lodash.get' should be added to package.json, or the 'lodash/get' require should be removed from printBuildError.js.

[gaearon]

Also worth looking into why this didn't fail CI.

[Timer]

Hi @svicalifornia; I'd love a bit more information -- are you ejected?

[Timer]

Also, what version of npm are you using?

Really, this shouldn't bomb out with npm >= 3 as it does dependency flattening and lodash is required by inquirer. Though it'd be technically correct to include lodash -- this should only blow up on npm < 3.

[Timer]

Fix up in #2938.

[Timer]

Released in react-dev-utils@3.1.1. Please upgrade!

[svicalifornia]

@Timer My colleague and I experienced the issue on systems running npm 4.2 and 5.1.0.

Thanks for the quick fix!

[Timer]

Are you ejected?

[svicalifornia]

We are not ejected, but we are using react-app-rewired to add loaders and plugins to our webpack config.

[Timer]

Hmm interesting. Non determinism at its finest haha.
Glad all is working now!