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
$ sudo npm install -g makemeasandwich
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
/usr/local/bin/makemeasandwich -> /usr/local/lib/node_modules/makemeasandwich/bin/makemeasandwich
>[email protected] install /usr/local/lib/node_modules/makemeasandwich/node_modules/phantomjs
> node install.js
sh: 1: node: not found
/usr/local/lib
└── (empty)
npm ERR! Linux 4.4.0-36-generic
npm ERR! argv "/usr/bin/nodejs""/usr/bin/npm""install""-g""makemeasandwich"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR![email protected] install: `node install.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] install script 'node install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the phantomjs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs phantomjs
npm ERR! Or if that isn't available, you can get their info via:npm ERR! npm owner ls phantomjsnpm ERR! There is likely additional logging output above.npm ERR! Please include the following file with any support request:npm ERR! /home/[email protected]/npm-debug.lognpm ERR! code 1[email protected]@mkelin-william:~$ sudo apt search phantomjsSorting... DoneFull Text Search... Donephantomjs/xenial,now 2.1.1+dfsg-1 amd64 [installed] minimalistic headless WebKit-based with JavaScript API
The text was updated successfully, but these errors were encountered:
Unable to install makemeasandwich on Ubuntu
Env
Output
The text was updated successfully, but these errors were encountered: