-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Can't start the project (fresh installation) #1111
Comments
Ok, so during installation I get this error - any ideas what to do please?
[execsync v1.0.2] Attempting to compile native extensions. |
@jakub2 - This looks to be some sort of funky Node/Windows problem. The very first thing I would try would be installing the current Node LTS version ( 4.x ) instead of node 6.8.x and see how it goes. |
That didn't help. Still the same problem. I'm on a Windows virtual machine. Any ideas? |
I'm also hitting this issue running windows. |
@d3viant0ne Awesome, thanks, let me know how it goes. |
yo @d3viant0ne any update on this? |
@gdi2290 - The issue @jakub2 & @adstep are seeing, I can't reproduce. The error that @jakub2 mentions tries to install The seed itself installs, compiles & functions as expected. |
Closing this for now as the issue is not present in #master If either of you are still having issues on windows, contact me directly & I will see if I can get you squared away. |
[x] bug report
I just cloned the repo and installed it. Then it failed to start. Below is my debug log.
It should start the project.
I'm behind a proxy (corporate environment). Do I need to set that up somewhere?
0 info it worked if it ends with ok
1 verbose cli [ 'C:\software\nodejs\node.exe',
1 verbose cli 'C:\software\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'server:dev:hmr' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'preserver:dev:hmr', 'server:dev:hmr', 'postserver:dev:hmr' ]
5 info lifecycle [email protected]
preserver:dev:hmr: [email protected]preserver:dev:hmr: no script for preserver:dev:hmr, continuing6 silly lifecycle [email protected]
7 info lifecycle [email protected]
server:dev:hmr: [email protected]server:dev:hmr: unsafe-perm in lifecycle true8 verbose lifecycle [email protected]
9 verbose lifecycle [email protected]
server:dev:hmr: PATH: C:\software\nodejs\node_modules\npm\bin\node-gyp-bin;c:\web\db-002\node_modules.bin;C:\software\cmder\bin;C:\software\cmder\vendor\git-for-windows\cmd;C:\software\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\software\cmder\vendor\conemu-maximus5;C:\software\cmder\vendor\conemu-maximus5\ConEmu;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Citrix\System32;C:\Program Files\Citrix\ICAService;C:\Program Files\AppSense\Application Manager\Agent\Plugins\EcaRulesEngine;C:\software\nodejs;C:\Users\ny563\AppData\Local\atom\bin;C:\software\Ruby23-x64\bin;C:\Users\ny563\AppData\Roaming\npm;C:\software\cmder\vendor\git-for-windows\usr\bin;C:\software\cmder\vendor\git-for-windows\usr\share\vim\vim74;C:\software\cmderserver:dev:hmr: CWD: c:\web\db-00210 verbose lifecycle [email protected]
11 silly lifecycle [email protected]
server:dev:hmr: Args: [ '/d /s /c', 'npm run server:dev -- --inline --hot' ]server:dev:hmr: Returned: code: 1 signal: null12 silly lifecycle [email protected]
13 info lifecycle [email protected]~server:dev:hmr: Failed to exec server:dev:hmr script
14 verbose stack Error: [email protected] server:dev:hmr:
npm run server:dev -- --inline --hot
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (C:\software\nodejs\node_modules\npm\lib\utils\lifecycle.js:255: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. (C:\software\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:877:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd c:\web\db-002
17 error Windows_NT 6.1.7601
18 error argv "C:\software\nodejs\node.exe" "C:\software\nodejs\node_modules\npm\bin\npm-cli.js" "run" "server:dev:hmr"
19 error node v6.8.1
20 error npm v3.10.8
21 error code ELIFECYCLE
22 error [email protected] server:dev:hmr:
npm run server:dev -- --inline --hot
22 error Exit status 1
23 error Failed at the [email protected] server:dev:hmr script 'npm run server:dev -- --inline --hot'.
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 angular2-webpack-starter package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error npm run server:dev -- --inline --hot
23 error You can get information on how to open an issue for this project with:
23 error npm bugs angular2-webpack-starter
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls angular2-webpack-starter
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
The text was updated successfully, but these errors were encountered: