-
Notifications
You must be signed in to change notification settings - Fork 85
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
ERR! libui-node@0.2.1 install: libui-download && autogypi && npm run build
#132
Comments
2019-04-14T18_36_30_231Z-debug.log Same issue here (MacOS) |
Same issue on Windows 10. 2019-04-25T23_47_32_803Z-debug.log |
Same issue here on Win10: |
Same issue here with Ubuntu 18.04, node v12.7.0, npm 6.10.0 I also tried completely uninstall node, npm, node-gyp and re-install them with nvm. |
I technically have the same issue, but I was also trying to install libui-node while behind a corporate firewall AND without admin privileges AND as a result having to use older node, v8.11.something, Windows 7, so I don't think my encounter with this issue quite applies but it's at least something to think about later. Works fine on my macOS High Sierra where I'm not behind a firewall and I have admin privileges, though. |
Directory permissions error?
Hope this is a helpful lead. |
Same issue here on Manjaro Linux 5.2.11-1-MANJARO. npm: v6.11.2 2019-09-29T00_13_03_537Z-debug.log I have base-devel loaded for compiling needs...
...and gtk3. I also tried installing libui-node globally with |
Extra data for me. Cannot install on Win10 1903 Node v12.13.0, seems to be nbind related. Gives a huge amount of errors like Also gives Warning: Please update all the dependencies this project uses, including nbind and the latest version of libui too, so that we may try to install this on newer Node versions, thanks! |
I get this error while trying to install libui-node with create-proton-app, I tried installing it externally but it failed that too.
I have both gtk3+ installed and build-essential
Platform: Xubuntu,
2019-02-09T14_07_45_513Z-debug.log
The text was updated successfully, but these errors were encountered: