Missing angular-cli-build.js in 1.0.0-beta.11-webpack

[serhiisol]

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

Mac OS X El Capitan 10.11.6

1. Versions. Please run ng --version. If there's nothing outputted, please run

angular-cli: 1.0.0-beta.11-webpack
node: 6.3.1
os: darwin x64

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

$ ng new webpack-test
$ ng serve

1. The log given by the failure. Normally this include a stack trace and some
   more information.

⇒  ng serve
(node:10190) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
No angular-cli-build.js found. Please see the transition guide: https://github.com/angular-cli/angular-cli/blob/master/TRANSITION.md#user-content-brocfile-transition.
Error: No angular-cli-build.js found. Please see the transition guide: https://github.com/angular-cli/angular-cli/blob/master/TRANSITION.md#user-content-brocfile-transition.
    at Class.module.exports.Task.extend.setupBroccoliBuilder (/Users/serhiysolonko/Development/Playground/wepback-test/node_modules/angular-cli/lib/models/builder.js:57:13)
    at Class.module.exports.Task.extend.init (/Users/serhiysolonko/Development/Playground/wepback-test/node_modules/angular-cli/lib/models/builder.js:89:10)
    at new Class (/Users/serhiysolonko/Development/Playground/wepback-test/node_modules/core-object/core-object.js:18:12)
    at Class.module.exports.Task.extend.run (/Users/serhiysolonko/Development/Playground/wepback-test/node_modules/angular-cli/lib/tasks/serve.js:15:19)
    at /Users/serhiysolonko/Development/Playground/wepback-test/node_modules/angular-cli/lib/commands/serve.js:64:24
    at lib$rsvp$$internal$$tryCatch (/Users/serhiysolonko/Development/Playground/wepback-test/node_modules/rsvp/dist/rsvp.js:1036:16)
    at lib$rsvp$$internal$$invokeCallback (/Users/serhiysolonko/Development/Playground/wepback-test/node_modules/rsvp/dist/rsvp.js:1048:17)
    at /Users/serhiysolonko/Development/Playground/wepback-test/node_modules/rsvp/dist/rsvp.js:331:11
    at lib$rsvp$asap$$flush (/Users/serhiysolonko/Development/Playground/wepback-test/node_modules/rsvp/dist/rsvp.js:1198:9)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)

PS. https://github.com/angular-cli/angular-cli/blob/master/TRANSITION.md#user-content-brocfile-transition - doesn't exist 😄

[mmgyce]

Did you type ng --version inside the webpack-test directory? I had the same error yesterday, I think when you create a new app with ng new myApp the angular-cli version installed locally is not the 1.0.0-beta.11-webpack version.

[NejcZdovc]

@serhiisol try following in your repo:

npm cache clean
npm install --save-dev angular-cli@webpack

[serhiisol]

the problem is that cli doesn't create this file at all. before I even run it, it doesn't exist

[serhiisol]

@NejcZdovc Why should I do that, if I have latest version of beta.11-webpack installed ?

[NejcZdovc]

@serhiisol you have webpack cli on global level, but probably not on local level. File angular-cli-build.js was used with systemjs, so you are not using correct cli version.

[NejcZdovc]

You can check it here #1528

[serhiisol]

Everything is installed from package.json, it has to be with correct versioning. I believe something is missing on cli side. Cause project is clean and it should just run.

[NejcZdovc]

@serhiisol You can also check it here

[itsmeprasanjit]

ng init did the trick but there are definately some bugs.

[serhiisol]

Ok, basically removing ^ from package.json

"angular-cli": "1.0.0-beta.11-webpack"

does trick, but that's not obvious at all, why npm installs incorrect angular-cli, it seems like without it, it installs another incompatible version.

[itsmeprasanjit]

npm install --save-dev angular-cli@webpack 👍

[serhiisol]

that's also not obvious at all 😄

[hansl]

This has been fixed already and is included in the nexrt release today or tomorrow.