Angular-cli: ng-cli .22 hangs, using angular v2.2.4

Created on 10 Dec 2016  路  15Comments  路  Source: angular/angular-cli

ng-cli .22 hangs, using angular v2.2.3


root@DESKTOP-VEUHFOL /cygdrive/c/msweb/studioDashboard
$ ng serve --port 4203
** NG Live Development Server is running on http://localhost:4203. **
 24% building modules 123/123 modules 0 active

OS?

Windows 10

Versions.

$ ng --version
angular-cli: 1.0.0-beta.22
node: 6.5.0
os: win32 x64

any updates on this?

regards

Sean.

Most helpful comment

Happens to me as well. Stuck on 20%

All 15 comments

I'm pretty sure angular-cli 22-1 is supposed to run on angular 2.2.3, not 2.2.4.

sorry updated 2.2.3, same issue...

Is this a brand new project or an existing one that was upgraded?

its a ng2 project (not ng1 upg to ng2)...
you can see the repo here:
https://github.com/born2net/studioDashboard

Angular 2 Kitchen sink: http://ng2.javascriptninja.io
and source@ https://github.com/born2net/Angular-kitchen-sink
Regards,

Sean

I'm also seeing it hang when upgrading from 21 to 22.

** NG Live Development Server is running on http://localhost:4200. **
 10% building modules 1/1 modules 0 activecan't resolve module ./ngsdk/api from /tmp/passit-frontend/src/app/app.module.ts
(node:2068) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: can't find symbol undefined exported from module /tmp/passit-frontend/src/app/ngsdk/api.ts, resolving symbol AppModule in /tmp/passit-frontend/src/app/app.module.ts, resolving symbol AppModule in /tmp/passit-frontend/src/app/app.module.ts
 19% building modules 79/79 modules 0 active

It will hang at 19% forever and not crash nor use any cpu. The resolve module is pretty trivial and works on 21. Assuming there is some underlying issue here.

ya its a show stopper... happens on all of projects, seems like .22 is a broken build!

You sure you're running angular 2.2.x and not 2.3? IIRC I had this issue when trying to use 2.3.

yes positive.
see attached

err

regards

Sean

if you have time please test as I really would like to use the new --hmr flag in .22

git clone https://github.com/born2net/studioDashboard.git
cd studioDashboard
npm i
ng serve <---- stuck

Happens to me as well. Stuck on 20%

Here as well, stuck at 22%

22% building modules 102/102 modules 0 active

Same here. Updated from a working .21 project to .22-1 following the recommended update process as always.

(node:5308) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule in ...

Fuck my life, just got the same error

ng-serve gets stuck!

error:
* NG Live Development Server is running on http://localhost:4200. *
10% building modules 2/2 modules 0 active(node:6294) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: CustomFormsModule is not an NgModule

20% building modules 91/91 modules 0 active gwebpack: wait until bundle finished:

OS : Win 10

Angular-Cli : "version": "1.0.0-beta.22-1"

Dev. dependencies:
"@angular/common": "2.2.3",
"@angular/compiler": "2.2.3",
"@angular/core": "2.2.3",
"@angular/forms": "2.2.3",
"@angular/http": "2.2.3",
"@angular/platform-browser": "2.2.3",
"@angular/platform-browser-dynamic": "2.2.3",
"@angular/router": "3.2.3",
"core-js": "^2.4.1",
"rxjs": "5.0.0-beta.12",
"ts-helpers": "^1.1.1",
"zone.js": "^0.6.23",
"@angular/material": "^2.0.0-alpha.10",
"@ng-bootstrap/ng-bootstrap": "^1.0.0-alpha.14",
"@progress/kendo-angular-upload": "^0.11.1",
"@telerik/kendo-theme-bootstrap": "^0.10.0",
"@telerik/kendo-theme-default": "^1.32.1",
"angularfire2": "^2.0.0-beta.6",
"firebase": "^3.6.1",
"font-awesome": "^4.7.0",
"hammerjs": "^2.0.8",
"ng2-material-select": "^0.1.4",
"ng2-tag-input": "^0.4.4",
"ng2-toastr": "^1.3.2",

"ng2-validation": "^3.0.1"

Npm version: 4.0.3

node-v7.2.1-x64.msi

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._

Was this page helpful?
0 / 5 - 0 ratings