Problem Windows 8.1
See original GitHub issue@kingvagabond , @parro-it , @mischnic , @kusti8 , @albe-rosado : Hi, I’ve been trying for days to run it on window 8.1, but I can not. Can someone help me? Has anyone ever tried to run it on windows? I would like to understand if only one of my problems or not. Package.json
{
"name": "my-app",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node_modules/.bin/babel-node index.js",
"build": "node_modules/.bin/babel index.js -d bin/",
"pack": "electron-builder --dir",
"dist": "electron-builder"
},
"dependencies": {
"proton-native": "latest"
},
"devDependencies": {
"electron-builder": "latest",
"babel-cli": "latest",
"babel-preset-env": "latest",
"babel-preset-stage-0": "latest",
"babel-preset-react": "latest"
},
"build": {
"protonNodeVersion": "current",
"mac": {
"identity": null
}
}
}
Project creation:
Run of the project:
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Troubleshoot Windows 8.1, Windows 8 or Windows 7 hangs ...
Check for updated firmware and drivers from your PC manufacturer. · Install all recommended updates for Windows using Windows Update. · Disconnect non-essential ......
Read more >9 Common Problems in Windows 8.1 | Network Wrangler
Windows 8 has another problem when it comes to displaying text. Many users have reported that some programs are displayed poorly on their ......
Read more >7 More Issues With Windows 8.1 That Can Be Fixed
7 More Issues With Windows 8.1 That Can Be Fixed · Broken Native App Tiles on the Start Screen · Broken Internet Connection...
Read more >Your PC needs to be repaired: Fix for Windows 8, 8.1
Fix #4: Rebuild the BCD · Insert the original installation DVD or USB Drive · Restart your computer · Boot from the disc/USB...
Read more >How to Troubleshoot Problems in Windows 8.1
Windows 8.1 Troubleshooters ... Before I show you some of the troubleshooters, let's see how to get to them in Windows 8.1. First,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@parro-it My issue is now resolved. Thanks to you comment in issue 95.
Also i am working on Windows 10 Pro.
Thanks again.
@kingvagabond , @parro-it , @mischnic , @kusti8 , @albe-rosado
Hi , i am also facing this issue when running the command
create-proton-app desktop-app
.I tried running this command even from administrator.
Prior to running this command i ran
npm install --global --production windows-build-tools
and it successfully installed ( ran this command as administrator ).Then i ran a command
npm install -g create-proton-app
, this also completed successfully (not as administrator ).When i ran this
create-proton-app desktop-app
, i got the same error as mentioned by @Angelk90 .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 ‘run’, 1 verbose cli ‘build’ ] 2 info using npm@5.6.0 3 info using node@v8.11.2 4 verbose run-script [ ‘prebuild’, ‘build’, ‘postbuild’ ] 5 info lifecycle libui-node@0.2.1~prebuild: libui-node@0.2.1 6 info lifecycle libui-node@0.2.1~build: libui-node@0.2.1 7 verbose lifecycle libui-node@0.2.1~build: unsafe-perm in lifecycle true 8 verbose lifecycle libui-node@0.2.1~build: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\structural_design\desktop-app\node_modules\libui-node\node_modules.bin;C:\structural_design\desktop-app\node_modules.bin;C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\structural_design\desktop-app\node_modules\libui-node\node_modules.bin;C:\structural_design\desktop-app\node_modules.bin;C:\Program Files\Java\jdk1.8.0_171\bin;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Google\Google Apps Sync;C:\Program Files\Google\Google Apps Migration;C:\Program Files\Git\cmd;C:\Program Files\apache-maven-3.5.3\bin;C:\Program Files\nodejs;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\CineForm\Tools;C:\Program Files (x86)\GoPro\Tools;C:\Ruby25-x64\bin;C:\Users\ajoshi\AppData\Local\Microsoft\WindowsApps;C:\Users\ajoshi\AppData\Local\GitHubDesktop\bin;C:\Users\ajoshi\AppData\Roaming\npm;C:\Program Files\Microsoft VS Code\bin 9 verbose lifecycle libui-node@0.2.1~build: CWD: C:\structural_design\desktop-app\node_modules\libui-node 10 silly lifecycle libui-node@0.2.1~build: Args: [ ‘/d /s /c’, ‘node-gyp configure build’ ] 11 silly lifecycle libui-node@0.2.1~build: Returned: code: 1 signal: null 12 info lifecycle libui-node@0.2.1~build: Failed to exec build script 13 verbose stack Error: libui-node@0.2.1 build:
node-gyp configure build
13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:285:16) 13 verbose stack at emitTwo (events.js:126:13) 13 verbose stack at EventEmitter.emit (events.js:214:7) 13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14) 13 verbose stack at emitTwo (events.js:126:13) 13 verbose stack at ChildProcess.emit (events.js:214:7) 13 verbose stack at maybeClose (internal/child_process.js:925:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) 14 verbose pkgid libui-node@0.2.1 15 verbose cwd C:\structural_design\desktop-app\node_modules\libui-node 16 verbose Windows_NT 10.0.14393 17 verbose argv “C:\Program Files\nodejs\node.exe” “C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js” “run” “build” 18 verbose node v8.11.2 19 verbose npm v5.6.0 20 error code ELIFECYCLE 21 error errno 1 22 error libui-node@0.2.1 build:node-gyp configure build
22 error Exit status 1 23 error Failed at the libui-node@0.2.1 build script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]Attached above is the log file.