Base solution for your next web application
Open Closed

Error when starting Angular 2 UI #2275


User avatar
0
geckotechnical created

Hi,

I have just created an ASP.NET Core and Angular 2 project and am trying to launch it for the first time. I have the .NET Core project working fine, but when I try and launch the Angular 2 UI project I get the following error:

C:\Development\ParkLeisure\Client>npm start

> [email protected] start C:\Development\ParkLeisure\Client
> ng serve --host 0.0.0.0 --port 4200 --live-reload-port 4201

Tried to find bootstrap code, but could not. Specify either statically analyzable bootstrap code or pass in an entryModule to the plugins options.
Error: Tried to find bootstrap code, but could not. Specify either statically analyzable bootstrap code or pass in an entryModule to the plugins options.
    at Object.resolveEntryModuleFromMain (C:\Development\ParkLeisure\Client\node_modules\@ngtools\webpack\src\entry_resolver.js:121:15)
    at AotPlugin._setupOptions (C:\Development\ParkLeisure\Client\node_modules\@ngtools\webpack\src\plugin.js:158:54)
    at new AotPlugin (C:\Development\ParkLeisure\Client\node_modules\@ngtools\webpack\src\plugin.js:17:14)
    at Object.exports.getWebpackNonAotConfigPartial (C:\Development\ParkLeisure\Client\node_modules\angular-cli\models\webpack-build-typescript.js:25:13)
    at new NgCliWebpackConfig (C:\Development\ParkLeisure\Client\node_modules\angular-cli\models\webpack-config.js:38:46)
    at Class.run (C:\Development\ParkLeisure\Client\node_modules\angular-cli\tasks\serve-webpack.js:23:22)
    at C:\Development\ParkLeisure\Client\node_modules\angular-cli\commands\serve.run.js:37:22
    at process._tickCallback (internal/process/next_tick.js:103:7)

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
npm ERR! node v7.4.0
npm ERR! npm  v4.0.5
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `ng serve --host 0.0.0.0 --port 4200 --live-reload-port 4201`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'ng serve --host 0.0.0.0 --port 4200 --live-reload-port 4201'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the abp-zero-template package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ng serve --host 0.0.0.0 --port 4200 --live-reload-port 4201
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs abp-zero-template
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls abp-zero-template
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Development\ParkLeisure\Client\npm-debug.log

npm-debug.log is as follows:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Development\ParkLeisure\Client\node_modules\.bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft Emulator Manager\1.0\;E:\Program Files (x86)\Brackets\command;E:\Program Files (x86)\Skype\Phone\;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files\Git\cmd;C:\Program Files\dotnet\;C:\Program Files\nodejs\;C:\Ruby23\bin;C:\Users\samc\AppData\Local\Programs\Python\Python35\Scripts\;C:\Users\samc\AppData\Local\Programs\Python\Python35\;C:\Users\samc\AppData\Local\Microsoft\WindowsApps;;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\samc\AppData\Roaming\npm
10 verbose lifecycle [email protected]~start: CWD: C:\Development\ParkLeisure\Client
11 silly lifecycle [email protected]~start: Args: [ '/d /s /c',
11 silly lifecycle   'ng serve --host 0.0.0.0 --port 4200 --live-reload-port 4201' ]
12 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: `ng serve --host 0.0.0.0 --port 4200 --live-reload-port 4201`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:885:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd C:\Development\ParkLeisure\Client
17 error Windows_NT 10.0.14393
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
19 error node v7.4.0
20 error npm  v4.0.5
21 error code ELIFECYCLE
22 error [email protected] start: `ng serve --host 0.0.0.0 --port 4200 --live-reload-port 4201`
22 error Exit status 1
23 error Failed at the [email protected] start script 'ng serve --host 0.0.0.0 --port 4200 --live-reload-port 4201'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the abp-zero-template package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     ng serve --host 0.0.0.0 --port 4200 --live-reload-port 4201
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs abp-zero-template
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls abp-zero-template
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

I have tried npm install again, as well as deleting node modules and then reinstalling, but always get the same error. I have noticed a warning message after it has installed packages:

npm WARN [email protected] requires a peer of webpack@^2.1.0-beta.19 but none was installed.

I tried installing that package version, but went round in a circle as different packages required peers of different versions and it seemingly overwrote each version every time I installed one.

Any help is appreciated.

Thanks


2 Answer(s)
  • User Avatar
    0
    mysterio21troy created

    Had the same issue as you, its mainly because of the angular-cli latest beta is still having issues.

    The current build from ABP is confirmed to work with angular-cli 1.0.0-beta.17

    If you wish to make it work, can do this:

    npm install -g rimraf
    rimraf node_modules
    

    Open up the project.json in the root of the angular abp app, and change

    "angular-cli": "^1.0.0-beta.17",
    

    to

    "angular-cli": "1.0.0-beta.17",
    

    then run

    npm i
    npm start
    

    This will force the usage of angular-cli to be the version that works with abp, probably better until it comes out of BETA.

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @mysterio21troy,

    Thank you for information you have shared :). According to my tests beta.21 also works without a problem.

    We have solved this issue, you can check the solution here <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-angular/issues/12">https://github.com/aspnetzero/aspnet-ze ... /issues/12</a>. We are also planning to add support for yarn, in order not to see such problems in the future.