search

naviapps / create-nw-react-app

Create NW.js React apps with no build configuration.
MIT License
144 stars 14 forks source link

Errors when doing npm start #2

Closed TheAwesomeGem closed 5 years ago

TheAwesomeGem commented 6 years ago

Here's the issue: https://i.gyazo.com/5302ac976520365b7be617a4c5deb644.png

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\TheAwesomeGem\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using npm@5.5.1
3 info using node@v6.10.2
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle react-testing@0.1.0~prestart: react-testing@0.1.0
6 info lifecycle react-testing@0.1.0~start: react-testing@0.1.0
7 verbose lifecycle react-testing@0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle react-testing@0.1.0~start: PATH: C:\Users\TheAwesomeGem\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;D:\react-testing\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\Git\cmd;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program Files (x86)\Ultraviolet Framework\v1.3\Tools\;C:\Python27;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\Skype\Phone\;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files\Microsoft DNX\Dnvm\;D:\LINQPad5;C:\Program Files\nodejs\;C:\Program Files\dotnet\;D:\Brackets\command;C:\Program Files (x86)\Universal Extractor;C:\Program Files (x86)\Universal Extractor\bin;D:\WorldPainter;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Users\TheAwesomeGem\AppData\Local\Microsoft\WindowsApps;C:\Users\TheAwesomeGem\AppData\Roaming\npm;C:\Gradle\bin;D:\Microsoft VS Code\bin
9 verbose lifecycle react-testing@0.1.0~start: CWD: D:\react-testing
10 silly lifecycle react-testing@0.1.0~start: Args: [ '/d /s /c', 'nw-react-scripts start' ]
11 silly lifecycle react-testing@0.1.0~start: Returned: code: 1  signal: null
12 info lifecycle react-testing@0.1.0~start: Failed to exec start script
13 verbose stack Error: react-testing@0.1.0 start: `nw-react-scripts start`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Users\TheAwesomeGem\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:280:16)
13 verbose stack     at emitTwo (events.js:106:13)
13 verbose stack     at EventEmitter.emit (events.js:191:7)
13 verbose stack     at ChildProcess.<anonymous> (C:\Users\TheAwesomeGem\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:106:13)
13 verbose stack     at ChildProcess.emit (events.js:191:7)
13 verbose stack     at maybeClose (internal/child_process.js:886:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
14 verbose pkgid react-testing@0.1.0
15 verbose cwd D:\react-testing
16 verbose Windows_NT 10.0.14393
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\TheAwesomeGem\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v6.10.2
19 verbose npm  v5.5.1
20 error code ELIFECYCLE
21 error errno 1
22 error react-testing@0.1.0 start: `nw-react-scripts start`
22 error Exit status 1
23 error Failed at the react-testing@0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
naviapis commented 6 years ago

It worked in my environment.

Approach 1 Are you using proxy settings? ・https://github.com/Microsoft/vscode/issues/2384 ・https://github.com/Microsoft/vscode/issues/28621

Approach 2 Please delete the /cache folder and retry.

Approach 3 Update the problem package to the latest version. (installed: v2.4.1)

npm install yauzl@2.9.1

Thanks.

TheAwesomeGem commented 6 years ago

Thank you. Will try that when I get a chance! And no, I am not using any proxy.

jasonbronson commented 6 years ago

I'm having this issue now and I'm behind a corporate firewall. Although dev tools states it returns a 200 request to the following plugin url https://liximomo.gallerycdn.vsassets.io/extensions/liximomo/sftp/0.8.10/1511144665016/Microsoft.VisualStudio.Services.Content.Details I then get the error message as well.

end of central directory record signature not found: Error: end of central directory record signature not found, at C:\Program Files\Microsoft VS Code\resources\app\node_modules\yauzl\index.js:183:14, at C:\Program Files\Microsoft VS Code\resources\app\node_modules\yauzl\index.js:618:5, at C:\Program Files\Microsoft VS Code\resources\app\node_modules\fd-slicer\index.js:32:7, at FSReqWrap.wrapper [as oncomplete] (fs.js:629:17) e.doShow @ messageService.ts:126 e.show @ messageService.ts:105 i.onError @ extensionEditor.ts:894 (anonymous) @ event.ts:410 (anonymous) @ event.ts:406 (anonymous) @ event.ts:222 i @ eventEmitter.ts:295 e._emitToSpecificTypeListeners @ eventEmitter.ts:162 e._emitEvents @ eventEmitter.ts:181 (anonymous) @ eventEmitter.ts:129 i @ eventEmitter.ts:295 e._emitToBulkListeners @ eventEmitter.ts:170 e._emitEvents @ eventEmitter.ts:176 e.emit @ eventEmitter.ts:196 (anonymous) @ actions.ts:237 v @ winjs.base.raw.js:1209 enter @ winjs.base.raw.js:901 _run @ winjs.base.raw.js:1068 _chainedError @ winjs.base.raw.js:1031 n @ winjs.base.raw.js:736 v @ winjs.base.raw.js:1209 enter @ winjs.base.raw.js:901 _run @ winjs.base.raw.js:1068 _error @ winjs.base.raw.js:1041 e.doRequest.n.TPromise.t.handlers.(anonymous function) @ ipc.ts:254 e.onMessage @ ipc.ts:319 (anonymous) @ ipc.ts:206 e.invoke @ callbackList.ts:36 e.fire @ event.ts:123 (anonymous) @ ipc.net.ts:82 emitOne @ events.js:96 emit @ events.js:191 readableAddChunk @ _stream_readable.js:178 Readable.push @ _stream_readable.js:136 onread @ net.js:560

Adding user/pass to the corp firewall proxy url doesn't help it.

"http.proxy": "http://192.1.1.1:80", "http.proxyStrictSSL": false, 

Tried to run basic npm command itself to verify if 
 /c/Program Files/Microsoft VS Code/resources/app
$ npm update
npm ERR! Error while executing:
npm ERR! C:\Program Files\Git\mingw64\bin\git.EXE ls-remote -h -t ssh://git@github.com/bpasero/chokidar.git
npm ERR!
npm ERR! ssh: connect to host github.com port 22: Connection timed out
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128

It was working and I could install extensions before. I'm able to update fine in VS code to latest version using proxy settings.

capture