Thursday, 16 March 2017

How to read an npm debug file

I don't know how to read an npm debug file , this what i've got when i tried to run an angular2 project , any help would be appreciated

ps : i runned other projects and it worked i don't know what is wrong with this one

        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 npm@3.10.8
        3 info using node@v6.10.0
        4 verbose config Skipping project config: C:\Users\Mayssa_B/.npmrc. (matches userconfig)
        5 verbose run-script [ 'prestart', 'start', 'poststart' ]
        6 info lifecycle myapp@0.0.0~prestart: myapp@0.0.0
        7 silly lifecycle myapp@0.0.0~prestart: no script for prestart, continuing
        8 info lifecycle myapp@0.0.0~start: myapp@0.0.0
        9 verbose lifecycle myapp@0.0.0~start: unsafe-perm in lifecycle true
       10 verbose lifecycle myapp@0.0.0~start: PATH: C:\Program       Files\nodejs\node_modules\npm\bin\node-gyp- bin;C:\Users\Mayssa_B\node_modules\.bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\AMD\ATI.ACE\Core-Static;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\MATLAB\R2010a\runtime\win32;C:\Program Files (x86)\MATLAB\R2010a\bin;C:\Program Files (x86)\MySQL\MySQL Fabric 1.5 & MySQL Utilities 1.5\;C:\Program Files (x86)\MySQL\MySQL Fabric 1.5 & MySQL Utilities 1.5\Doctrine extensions for PHP\;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\Git\cmd;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Program Files\nodejs\;C:\Program Files\Git\bin;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\Mayssa_B\AppData\Roaming\npm
        11 verbose lifecycle myapp@0.0.0~start: CWD: C:\Users\Mayssa_B
    12 silly lifecycle myapp@0.0.0~start: Args: [ '/d /s /c', 'ng serve' ]
    13 silly lifecycle myapp@0.0.0~start: Returned: code: 1  signal: null
    14 info lifecycle myapp@0.0.0~start: Failed to exec start script
    15 verbose stack Error: myapp@0.0.0 start: `ng serve`
    15 verbose stack Exit status 1
    15 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
    15 verbose stack     at emitTwo (events.js:106:13)
    15 verbose stack     at EventEmitter.emit (events.js:191:7)
    15 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
    15 verbose stack     at emitTwo (events.js:106:13)
    15 verbose stack     at ChildProcess.emit (events.js:191:7)
    15 verbose stack     at maybeClose (internal/child_process.js:877:16)
    15 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
    16 verbose pkgid myapp@0.0.0
    17 verbose cwd C:\Users\Mayssa_B\Desktop\angular2-express-mysql-typescript-seed-master
    18 error Windows_NT 6.3.9600
    19 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
    20 error node v6.10.0
    21 error npm  v3.10.8
    22 error code ELIFECYCLE
    23 error myapp@0.0.0 start: `ng serve`
    23 error Exit status 1
    24 error Failed at the myapp@0.0.0 start script 'ng serve'.
    24 error Make sure you have the latest version of node.js and npm installed.
    24 error If you do, this is most likely a problem with the myapp package,
    24 error not with npm itself.
    24 error Tell the author that this fails on your system:
    24 error     ng serve
    24 error You can get information on how to open an issue for this project with:
    24 error     npm bugs myapp
    24 error Or if that isn't available, you can get their info via:
    24 error     npm owner ls myapp
    24 error There is likely additional logging output above.
    25 verbose exit [ 1, true ]



via B.Mayssa

No comments:

Post a Comment