Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
serhiisol opened this issue Aug 5, 2016 · 25 comments
Closed

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

serhiisol opened this issue Aug 5, 2016 · 25 comments

Comments

@serhiisol
Copy link
Contributor

serhiisol commented Aug 5, 2016

  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
Copy link

mmgyce commented Aug 5, 2016

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
Copy link

NejcZdovc commented Aug 5, 2016

@serhiisol try following in your repo:

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

@serhiisol
Copy link
Contributor Author

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

@serhiisol
Copy link
Contributor Author

serhiisol commented Aug 5, 2016

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

@NejcZdovc
Copy link

NejcZdovc commented Aug 5, 2016

@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
Copy link

You can check it here #1528

@serhiisol
Copy link
Contributor Author

serhiisol commented Aug 5, 2016

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
Copy link

NejcZdovc commented Aug 5, 2016

@serhiisol You can also check it here

@itsmeprasanjit
Copy link

itsmeprasanjit commented Aug 5, 2016

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

@serhiisol
Copy link
Contributor Author

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
Copy link

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

@serhiisol
Copy link
Contributor Author

that's also not obvious at all 😄

@hansl
Copy link
Contributor

hansl commented Aug 10, 2016

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

@hansl hansl closed this as completed Aug 10, 2016
cmermingas added a commit to cmermingas/connect-four-webpack that referenced this issue Aug 13, 2016
@cmermingas
Copy link

I didn't know my commit in my little learning project would show up here just because I mentioned this issue for my own reference :)

Anyway, I followed the instructions here to install and create a project from scratch. I also followed the recommendations above: npm cache clean inside the project, then removed the caret (^) from package.json, reran npm install. But I still get this error when running ng github-pages:deploy

@srivasrk
Copy link

@cmermingas . I am facing the same issue. I have tried npm install --save-dev angular-cli@webpack. Also removed the crate in package.json.
Don't know whats wrong. Been a long day already.
ng github-pages:deploy still throws the error: "no angular cli-build.js found"

@stefanaerts
Copy link

same problem for me with angular-cli@1.0.0-beta.11-webpack.2
--steps ---------------

  1. ng new 'projectname' ,
  2. create repo on github
  3. git commit -m 'initial commit with angular-cli generated code'
  4. git push -u origin master

5) ng github-pages:deploy

ng github-pages:deploy throws the error: "no angular cli-build.js found"

@stefanaerts
Copy link

and i did all of it, install angular-cli local puts ^ in front but that doesnt work.
Then i changed the local package.json again with ^ removed, but still the same error.
i did npm install and repeated all the steps again, still the same error.
So it would be very nice if somebody of the angular-cli developers can explain whats going on. Thx.

@filipesilva
Copy link
Contributor

@cmermingas @srivasrk @stefanaerts there was a separate problem affecting the github deploy functionality that has been fixed in #1633 and is pending release.

@renevall
Copy link

I'm getting this error too.

@elvirdolic
Copy link

elvirdolic commented Aug 31, 2016

This error is still not fixed

with "angular-cli": "^1.0.0-beta.11-webpack.8", my build server fails

without it works

@Blak3Nick
Copy link

I had to install awesome-typescript-loader as a dev dependency after running
npm install --save-dev angular-cli@webpack. Finally got the project up and running again.

@pomeara
Copy link

pomeara commented Oct 5, 2016

I'm having this problem today, the angular-cli seems like a great idea but continues to have numerous bugs

@serhiisol
Copy link
Contributor Author

Guys, this ticket already closed due to new releases of cli (for instance with beta 16 everything works as it should)

PS. Try to update to latest, should help

@sutin1234
Copy link

where angular-cli-build.json: in project angular-cli

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests