I actually had thought that I'd mistyped 'npm start' at first, but no: C:\sandbox\ang2\quick>npm start
> [email protected] start C:\sandbox\ang2\quick > concurrent "npm run tsc:w" "npm run lite" [0] 'np' is not recognized as an internal or external command, [0] operable program or batch file. Error occured when executing command: np Error: spawn np ENOENT at notFoundError (C:\sandbox\ang2\quick\node_modules\concurrently\node_modules\cross-spawn\node_ modules\cross-spawn-async\lib\enoent.js:8:11) at verifyENOENT (C:\sandbox\ang2\quick\node_modules\concurrently\node_modules\cross-spawn\node_m odules\cross-spawn-async\lib\enoent.js:43:16) at ChildProcess.cp.emit (C:\sandbox\ang2\quick\node_modules\concurrently\node_modules\cross-spaw n\node_modules\cross-spawn-async\lib\enoent.js:30:19) at Process.ChildProcess._handle.onexit (child_process.js:789:12) I deleted my folder and started again, and kept a copy of the install log. I'm not sure if any of the following errors have anything to do with it: c:\users\jennifer_ayers\.node-gyp\0.10.13\deps\uv\include\uv-private/uv-win.h(32): fatal error C1083: Cannot open include file: 'winsock2.h': No such file or directory [C:\sandbox\ang2\quick\node_modules\lite-server\node_modules\browser-sync\node_modules\socket.io\node_modules\engine.io\node_modules\ws\node_modules\utf-8-validate\build\binding.sln] c:\users\jennifer_ayers\.node-gyp\0.10.13\deps\uv\include\uv-private/uv-win.h(32): fatal error C1083: Cannot open include file: 'winsock2.h': No such file or directory [C:\sandbox\ang2\quick\node_modules\lite-server\node_modules\browser-sync\node_modules\socket.io\node_modules\engine.io\node_modules\ws\node_modules\bufferutil\build\binding.sln] Project : warning PRJ0018: The following environment variables were not found: [C:\sandbox\ang2\quick\node_modules\lite-server\node_modules\browser-sync\node_modules\socket.io\node_modules\engine.io\node_modules\ws\node_modules\utf-8-validate\build\binding.sln] Any other suggestions? On Tuesday, January 26, 2016 at 2:29:52 PM UTC-8, Jennifer Ayres wrote: > > Ok, so I'm following the Angular 2 walkthrough, and I'm having trouble > with the npm start: > > > [email protected] start C:\sandbox\ang2\quick > > concurrent "npm run tsc:w" "npm run lite" > > [0] 'np' is not recognized as an internal or external command, > [0] operable program or batch file. > Error occured when executing command: np > Error: spawn np ENOENT > at notFoundError > (C:\sandbox\ang2\quick\node_modules\concurrently\node_modul > es\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:8:11) > at verifyENOENT > (C:\sandbox\ang2\quick\node_modules\concurrently\node_module > s\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:43:16) > at ChildProcess.cp.emit > (C:\sandbox\ang2\quick\node_modules\concurrently\nod > e_modules\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:30:19) > at Process.ChildProcess._handle.onexit (child_process.js:789:12) > [1] 'run' is not recognized as an internal or external command, > [1] operable program or batch file. > Error occured when executing command: run > Error: spawn run ENOENT > at notFoundError > (C:\sandbox\ang2\quick\node_modules\concurrently\node_modul > es\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:8:11) > at verifyENOENT > (C:\sandbox\ang2\quick\node_modules\concurrently\node_module > s\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:43:16) > at ChildProcess.cp.emit > (C:\sandbox\ang2\quick\node_modules\concurrently\nod > e_modules\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:30:19) > at Process.ChildProcess._handle.onexit (child_process.js:789:12) > [2] '"tsc:w\""' is not recognized as an internal or external command, > [2] operable program or batch file. > Error occured when executing command: tsc:w" > Error: spawn tsc:w" ENOENT > at notFoundError > (C:\sandbox\ang2\quick\node_modules\concurrently\node_modul > es\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:8:11) > at verifyENOENT > (C:\sandbox\ang2\quick\node_modules\concurrently\node_module > s\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:43:16) > at ChildProcess.cp.emit > (C:\sandbox\ang2\quick\node_modules\concurrently\nod > e_modules\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:30:19) > at Process.ChildProcess._handle.onexit (child_process.js:789:12) > [3] 'np' is not recognized as an internal or external command, > [3] operable program or batch file. > Error occured when executing command: np > Error: spawn np ENOENT > at notFoundError > (C:\sandbox\ang2\quick\node_modules\concurrently\node_modul > es\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:8:11) > at verifyENOENT > (C:\sandbox\ang2\quick\node_modules\concurrently\node_module > s\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:43:16) > at ChildProcess.cp.emit > (C:\sandbox\ang2\quick\node_modules\concurrently\nod > e_modules\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:30:19) > at Process.ChildProcess._handle.onexit (child_process.js:789:12) > [4] 'run' is not recognized as an internal or external command, > [4] operable program or batch file. > Error occured when executing command: run > Error: spawn run ENOENT > at notFoundError > (C:\sandbox\ang2\quick\node_modules\concurrently\node_modul > es\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:8:11) > at verifyENOENT > (C:\sandbox\ang2\quick\node_modules\concurrently\node_module > s\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:43:16) > at ChildProcess.cp.emit > (C:\sandbox\ang2\quick\node_modules\concurrently\nod > e_modules\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:30:19) > at Process.ChildProcess._handle.onexit (child_process.js:789:12) > [5] '"lite\""' is not recognized as an internal or external command, > [5] operable program or batch file. > Error occured when executing command: lite" > Error: spawn lite" ENOENT > at notFoundError > (C:\sandbox\ang2\quick\node_modules\concurrently\node_modul > es\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:8:11) > at verifyENOENT > (C:\sandbox\ang2\quick\node_modules\concurrently\node_module > s\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:43:16) > at ChildProcess.cp.emit > (C:\sandbox\ang2\quick\node_modules\concurrently\nod > e_modules\cross-spawn\node_modules\cross-spawn-async\lib\enoent.js:30:19) > at Process.ChildProcess._handle.onexit (child_process.js:789:12) > [4] run exited with code 1 > [3] np exited with code 1 > [2] tsc:w" exited with code 1 > [1] run exited with code 1 > [0] np exited with code 1 > [5] lite" exited with code 1 > npm ERR! weird error 1 > npm ERR! not ok code 0 > > Appreciate any suggestions on where to start. > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
