You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fails at install step. npm ERR! Failed at the [email protected] install script.
Stdout log
Result (npm install proton-native)
Installing packages... This may take a few minutes...
# [snip]
ERR! [email protected] install: `libui-download && autogypi && npm run build`
npm ERR! Failed at the [email protected] install script.
$ npm install -g [email protected]
> [email protected] install /usr/local/lib/node_modules/libui-node
> libui-download && autogypi && npm run build
Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/libui-node/.libui'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `libui-download && autogypi && npm run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-08-15T09_33_49_101Z-debug.log
The text was updated successfully, but these errors were encountered:
Experiencing the same issue on node 12.9.0 -- attached my log here. Seems to be related to gup, and happens independent of "create-proton-app". I get the same results just using npm i -S proton-native 2019-08-27T18_11_27_850Z-debug.log
Issue:
Installing proton-native fails on installing package [email protected]
This seems to be a problem with the dependency libui-node.
See issue here:
parro-it/libui-node#132
Details
Installed depends:
Related
libui-download && autogypi && npm run build
parro-it/libui-node#132Step to reproduce
sudo apt-get install libgtk-3-dev build-essential
npm install create-proton-app
Fails at install step.
npm ERR! Failed at the [email protected] install script.
Stdout log
Result (npm install proton-native)
Manually installing
[email protected]
The text was updated successfully, but these errors were encountered: