Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Linux x64

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.19-3
node: 6.9.1
os: linux x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

My project is stable right now in beta.17 trying to use beta.18 or beta.19-3 on npm.

The log given by the failure.

Normally this include a stack trace and some more information.
No building error. It happens on runtime.

Mention any other details that might be useful.

Webpack seems to wrongly resolve indirect dependencies. To be more precise:
0) Grab a ng new project

1. Install a package X with dependency Y (let's call it oldY).
2. install package Y (lets call it newY).
3. On ng serve (looking at the main bundle if you wish), package X will receive newY instead.

I personally did these tests for packages X = jsonapi-serializer, Y = lodash (or Y = bluebird)

This error seems to be related to #2291. Commenting out the line changed in this PR makes webpack resolve correctly as before.

---

Thanks! We'll be in touch soon.