This is what's causing it:
We should figure out how to call the installer ourselves.
A workaround is to not install Forge as root. Try the alternative methods to create an Electron app project with Forge as mentioned in the README.
@malept I tried installing as not root and i get:
`npm ERR! Linux 4.10.0-28-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "electron-forge"
npm ERR! node v6.11.4
npm ERR! npm v3.10.10
npm ERR! path /usr/lib/node_modules
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/usr/lib/node_modules'
npm ERR! at Error (native)
npm ERR! { Error: EACCES: permission denied, access '/usr/lib/node_modules'
npm ERR! at Error (native)
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'access',
npm ERR! path: '/usr/lib/node_modules' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR! /home/devarsh/npm-debug.log`
@devarshjoshi what I've done in the past on Linux for these Node tools that suggest installing globally is run (as not root) mkdir -p ~/.local && npm config set prefix ~/.local. This should set the default install prefix to $HOME/.local which you should have permissions to install to.
@malept awesome thanks looks like that worked!! thanks for the quick reply.
Is this still an open issue? I have spent the last few hours trying solutions mentioned here and elsewhere. Is there a known configuration for ubuntu/npm/node.js under which electron-forge will install?
It's open, therefore it's an open issue. I still haven't found time to work on it, but I would be happy to review a PR to rewrite the tabtab install script.
The instructions in https://github.com/electron-userland/electron-forge/issues/321#issuecomment-338316565 are known to work.
Thanks, Mark. I will revisit the 321 comments.
Most helpful comment
@devarshjoshi what I've done in the past on Linux for these Node tools that suggest installing globally is run (as not root)
mkdir -p ~/.local && npm config set prefix ~/.local. This should set the default install prefix to$HOME/.localwhich you should have permissions to install to.