I am trying to build https://github.com/Microsoft/vscode from the source, but I am not sure exactly what to do. When I ran scripts\npm.bat install, it completed successfully. Then I ran scripts\code.bat and a stranger window showed up. It is it the compiled version? It did not seem to work correctly.
How can I create full build? The page:
https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run-from-source
Does not offered how to create an executable from the source. When I run scripts\npm.bat install what should happen? For now I only see it create the folder out/out-build within some javascript files, as showed bellow. What are those files and what I do with them?
Later I tried to ran the scripts\code.bat and created an executable similar in size to the stable version on the folder .build\electron:
But when I ran npm run watch, this error is throw:
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
npm ERR! Windows_NT 10.0.15063
npm ERR! argv "D:\\User\\Documents\\Nodejs\\bin\\node.exe" "D:\\User\\Documents\\Nodejs\\bin\\node_modules\\npm\\bin\\npm-cli.js" "run" "watch"
npm ERR! node v6.11.0
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! code-oss-dev#1.15.0 watch: `gulp watch --max_old_space_size=4096`
npm ERR! Exit status 3
npm ERR!
npm ERR! Failed at the code-oss-dev#1.15.0 watch script 'gulp watch --max_old_space_size=4096'.
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 code-oss-dev package,
npm ERR! not with npm itself.
I found the other question:
How to build release vscode version
But I could not figure it out correctly how to build it. Forehand I figured out the following steps to setup the environment:
Install NodeJS and npm. See
the tutorial How to Install Node.js® and NPM on
Windows
Run this command npm install --global --production windows-build-tools from cmd line as
Administrator. See npm install error - MSB3428: Could not load the Visual C++ component
“VCBuild.exe”
Install gulp. See gulpjs/gulp#Getting
Started
Steps to Reproduce
git clone https://github.com/Microsoft/vscode
cd vscode
scripts\npm.bat install
npm run watch
Outputs: F:\vscode>npm run watch
File npm-debug.log:
1) When I ran the command scripts\npm.bat install for the first time, this was the output:
F:\vscode>scripts\npm.bat install
2) When I ran the command scripts\npm.bat install for the after the first time, this was the output:
F:\vscode>scripts\npm.bat install
3) When I ran the command scripts\code.bat, this was the output:
F:\vscode>scripts\code.bat
And the following window showed up:
4) When I ran the command npm owner ls code-oss-dev as asked by the npm run watch error message, this was the output:
F:\vscode>npm owner ls code-oss-dev
npm ERR! owner ls Couldn't get owner data code-oss-dev
npm ERR! Windows_NT 10.0.15063
npm ERR! argv "D:\\User\\Documents\\Nodejs\\bin\\node.exe" "D:\\User\\Documents\\Nodejs\\bin\\node_modules\\npm\\bin\\npm-cli.js" "owner" "ls" "code-oss-dev"
npm ERR! node v6.11.0
npm ERR! npm v3.10.10
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/code-oss-dev
npm ERR! 404
npm ERR! 404 'code-oss-dev' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR! F:\vscode\npm-debug.log
F:\vscode>
5) When I ran the command npm bugs code-oss-dev as asked by the npm run watch error message, this was the error output:
F:\vscode>npm bugs code-oss-dev
npm ERR! Windows_NT 10.0.15063
npm ERR! argv "D:\\User\\Documents\\Nodejs\\bin\\node.exe" "D:\\User\\Documents\\Nodejs\\bin\\node_modules\\npm\\bin\\npm-cli.js" "bugs" "code-oss-dev"
npm ERR! node v6.11.0
npm ERR! npm v3.10.10
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/code-oss-dev
npm ERR! 404
npm ERR! 404 'code-oss-dev' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR! F:\vscode\npm-debug.log
F:\vscode>
6) I also ran the command gulp, this was the output:
F:\vscode>gulp
7) When I ran the command gulp compile-client-build, this was the output:
F:\vscode>gulp compile-client-build
[08:36:37] Using gulpfile F:\vscode\gulpfile.js
[08:36:37] Starting 'clean-client-build'...
[08:36:37] Finished 'clean-client-build' after 49 ms
[08:36:37] Starting 'compile-client-build'...
[08:36:38] Starting compilation...
[08:50:08] [monaco.d.ts] Starting monaco.d.ts generation
[08:50:12] [monaco.d.ts] Finished monaco.d.ts generation
[08:50:12] Finished compilation with 0 errors after 814540 ms
[08:50:12] Finished 'compile-client-build' after 14 min
8) When I ran the command gulp vscode-win32-ia32, this was the error output:
[02:15:28] Starting 'vscode-win32-ia32'...
internal/streams/legacy.js:59
throw er; // Unhandled stream error in pipe.
^
Error: read ECONNRESET
at exports._errnoException (util.js:1018:11)
at TLSWrap.onread (net.js:568:26)
F:\vscode>gulp vscode-win32-ia32
9) When I ran the command gulp vscode-win32-x64, this was the error output:
[03:02:59] Starting 'vscode-win32-x64'...
internal/streams/legacy.js:59
throw er; // Unhandled stream error in pipe.
^
Error: read ECONNRESET
at exports._errnoException (util.js:1018:11)
at TLSWrap.onread (net.js:568:26)
F:\vscode>gulp vscode-win32-x64
10) When I ran the command npm run gulp -- vscode-win32-ia32, this was the error output:
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
npm ERR! Windows_NT 10.0.15063
npm ERR! argv "D:\\User\\Documents\\Nodejs\\bin\\node.exe" "D:\\User\\Documents\\Nodejs\\bin\\node_modules\\npm\\bin\\npm-cli.js" "run" "gulp" "--" "vscode-win32-ia32"
npm ERR! node v6.11.0
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! code-oss-dev#1.15.0 gulp: `gulp --max_old_space_size=4096 "vscode-win32-ia32"`
npm ERR! Exit status 3
F:\vscode>npm run gulp -- vscode-win32-ia32
File npm-debug.log for the command npm run gulp -- vscode-win32-ia32 just above.
11) When I ran the command gulp watch --max-old-space-size=4096, this was the output, and the program hanged on this line:
F:\vscode>gulp watch --max-old-space-size=4096
npm version
F:\vscode>npm --version
3.10.10
F:\vscode>node --version
v6.11.0
F:\vscode>ver
Microsoft Windows [Version 10.0.15063]
F:\vscode>python --version
Python 2.7.13 :: Continuum Analytics, Inc.
VSCode Version: code-oss-dev#1.15.0
OS Version: Windows 10 build 15063 x64
Originally posted on: Failed at the code-oss-dev#1.15.0 watch script 'gulp watch --max_old_space_size=4096'
Related issues:
Development Environment Improvements (code.bat/code.sh)
Errors Compiling from Source on Arch Linux
Unable to setup vscode locally
Debug Batch (.bat) files
"JavaScript heap out of memory" when building on RHEL-7
Failed at the electron-mksnapshot#1.6.0 install script
Unhandled stream error in pipe
stream.js:74 throw er; // Unhandled stream error in pipe.
Node.js – events js 72 throw er unhandled 'error' event
vscode-win32-ia32 build failure: JavaScript heap out of memory
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
npm/npm#FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
nodejs/node#FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
The problem seems to be the outdated version 6.11.0 of nodejs used. From the issue: Failed at the code-oss-dev#1.15.0 watch script 'gulp watch --max_old_space_size=4096' on the VSCode issue tracker, we may follow the steps:
Install Node 7.9.0
git clean -xfd .
git pull
.\scripts\npm.bat install
Then, if there are no errors:
npm run watch
Run it until it tells you compilation succeeded. Then:
.\scripts\code.bat
When I try to follow the instructions, I get:
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Visual Studio installation to use
gyp ERR! stack at VisualStudioFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:121:47)
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:74:16
gyp ERR! stack at VisualStudioFinder.findVisualStudio2013 (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:351:14)
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:70:14
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:372:16
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\util.js:54:7
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\util.js:33:16
gyp ERR! stack at ChildProcess.exithandler (child_process.js:310:5)
gyp ERR! stack at ChildProcess.emit (events.js:315:20)
gyp ERR! stack at maybeClose (internal/child_process.js:1021:16)
gyp ERR! System Windows_NT 10.0.17763
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd F:\code\vscode\node_modules\native-watchdog
Not sure why, but it seems as if node-gyp cannot find visual studio.
Related
I'm trying to deploy my first project on a server with C Panel, I followed this guide but when I press "run JS script" I get the following error:
returncode: 126
stdout:
> node-mysql#1.0.0 start /home/manteia1/Area_SFTP
> nodemon app.js
stderr:
npm WARN lifecycle The node binary used for scripts is /home/manteia1/nodevenv/Area_SFTP/8/bin/node but npm is using /opt/alt/alt-nodejs8/root/usr/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
sh: /home/manteia1/Area_SFTP/node_modules/.bin/nodemon: Permission denied
npm ERR! code ELIFECYCLE
npm ERR! errno 126
npm ERR! node-mysql#1.0.0 start: `nodemon app.js`
npm ERR! Exit status 126
npm ERR!
npm ERR! Failed at the node-mysql#1.0.0 start 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! /home/manteia1/.npm/_logs/2021-02-10T14_38_41_625Z-debug.log
I will be very specific and will divide my question into points.
I am running a Ubuntu 14.04 LTS machine with node.js on board
1. What I want to achieve in overall:
I want to install the iotivity-node npm package on my local computer
2. What is not working:
During the installation I get the following logs and errors:
iotivity-node#1.2.1-1 install
/usr/local/lib/node_modules/iotivity-node node-gyp rebuild
make: Entering directory
`/usr/local/lib/node_modules/iotivity-node/build' ACTION Building CSDK
iotivity-installed Cloning into
'/usr/local/lib/node_modules/iotivity-node/iotivity-native'... remote:
Counting objects: 3825, done remote: Finding sources: 100% (3825/3825)
remote: Total 3825 (delta 281), reused 1993 (delta 281) Receiving
objects: 100% (3825/3825), 13.87 MiB | 365.00 KiB/s, done. Resolving
deltas: 100% (281/281), done. Checking connectivity... done. Note:
checking out '0c90ca6ffcbb6a2c56c977ec11bebb7b1d14053b'.
You are in 'detached HEAD' state. You can look around, make
experimental changes and commit them, and you can discard any commits
you make in this state without impacting any branches by performing
another checkout.
If you want to create a new branch to retain commits you create, you
may do so (now or later) by using -b with the checkout command again.
Example:
git checkout -b new_branch_name
Cloning into
'/usr/local/lib/node_modules/iotivity-node/iotivity-native/extlibs/tinycbor/tinycbor'...
error: RPC failed; result=35, HTTP code = 0 fatal: The remote end hung
up unexpectedly make: *** [iotivity-installed] Error 128 make: Leaving
directory /usr/local/lib/node_modules/iotivity-node/build' gyp ERR!
build error gyp ERR! stack Error:make` failed with exit code: 2 gyp
ERR! stack at ChildProcess.onExit
(/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at emitTwo (events.js:106:13) gyp ERR! stack at
ChildProcess.emit (events.js:191:7) gyp ERR! stack at
Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Linux 3.13.0-107-generic gyp ERR! command
"/usr/local/bin/node"
"/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js"
"rebuild" gyp ERR! cwd /usr/local/lib/node_modules/iotivity-node gyp
ERR! node -v v6.4.0 gyp ERR! node-gyp -v v3.4.0 gyp ERR! not ok npm
ERR! Linux 3.13.0-107-generic npm ERR! argv "/usr/local/bin/node"
"/usr/local/bin/npm" "install" "-g" "iotivity-node" npm ERR! node
v6.4.0 npm ERR! npm v3.10.8 npm ERR! code ELIFECYCLE
npm ERR! iotivity-node#1.2.1-1 install: node-gyp rebuild npm ERR!
Exit status 1 npm ERR! npm ERR! Failed at the iotivity-node#1.2.1-1
install script 'node-gyp rebuild'. 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 iotivity-node package, npm ERR! not
with npm itself. npm ERR! Tell the author that this fails on your
system: npm ERR! node-gyp rebuild npm ERR! You can get information
on how to open an issue for this project with: npm ERR! npm bugs
iotivity-node npm ERR! Or if that isn't available, you can get their
info via: npm ERR! npm owner ls iotivity-node npm ERR! There is
likely additional logging output above.
3. Did anyone run across this issue while installing iotivity-node and if yes how you have resolved it? Thank you in advance for your answers.
fatal: The remote end hung up unexpectedly
This means it failed to download the code it needs. Just try again - it should work.
Im trying to install socket.io into my beagleboneblack, system says my node -v is v0.8.22 and for installation should be at least higher than 0.10.0.
but I can`t upgrade my node.
For installing socket.io, I enter the following text:
/usr/bin/ntpdate -b -s -u pool.ntp.org
cd /var/lib/cloud9
npm install socket.io
cp bonescript-socketio/* /var/lib/cloud9
Error message:
http GET https://registry.npmjs.org/socket.io-parser/2.3.1
WARN engine object-assign#4.1.0: wanted {"node":">=0.10.0"} (current: {"node":"v0.8.22","npm":"1.2.14"})
ERR! fetch failed https://registry.npmjs.org/ms/-ms-0.7.1.tgz
Error message upon completion:
npm ERR! Error: getaddrinfo ENOTFOUND
npm ERR! at errnoException (dns.js:37:11)
npm ERR! at Object.onanswer [as oncomplete] (dns.js:124:16)
npm ERR! If you need help, you may report this log at:
npm ERR! <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR! <npm-#googlegroups.com>
npm ERR! System Linux 3.8.13
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "socket.io"
npm ERR! cwd /var/lib/cloud9
npm ERR! node -v v0.8.22
npm ERR! npm -v 1.2.14
npm ERR! syscall getaddrinfo
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm http GET https://registry.npmjs.org/ms/-/ms-0.7.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/ms/-/ms-0.7.1.tgz
npm http GET https://registry.npmjs.org/ms/-/ms-0.7.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/ms/-/ms-0.7.1.tgz
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /var/lib/cloud9/npm-debug.log
npm ERR! not ok code 0
for node upgrade I've tried
opkg update
but server seems to be down..
Appreciate your attention.
If you type in:
cat /etc/dogtag
you will get a readout. This readout tells you what version of Linux you have on your machine. If you go to http://elinux.org/Beagleboard:BeagleBoneBlack_Debian, the images are updated regularly for the BBB and BBG boards.
Try to update your image and then upgrade to the newer version of socket.io.
Seth
P.S. If this does not work, please let me know.
I recently switched to Ubuntu 14.04, and also worked on my Mac machine. This project is cloned from the same repo, but behaves differently on two machines. I have no clue why, please help me.
I used this line to hashed my password, and it works fine on my mac machine.
var hashed = crypto.pbkdf2Sync(entered,this.salt,12000,128).toString('hex');
However, in Ubuntu, it gives following errors:
> node ./bin/www
crypto.js:574
var ret = binding.PBKDF2(password, salt, iterations, keylen, digest);
^
TypeError: Not a buffer
at TypeError (native)
at pbkdf2 (crypto.js:574:23)
at Object.exports.pbkdf2Sync (crypto.js:553:10)
at model.<anonymous> (/media/linux/app/dataModel/userModel.js:30:33)
at _next (/media/linux/app/node_modules/mongoose/node_modules/hooks-fixed/hooks.js:62:30)
at fnWrapper (/media/linux/app/node_modules/mongoose/node_modules/hooks-fixed/hooks.js:186:18)
at model.Object.defineProperty.value.fn (/media/linux/app/node_modules/mongoose/lib/schema.js:215:9)
at _next (/media/linux/app/node_modules/mongoose/node_modules/hooks-fixed/hooks.js:62:30)
at fnWrapper (/media/linux/app/node_modules/mongoose/node_modules/hooks-fixed/hooks.js:186:18)
at /media/linux/app/node_modules/mongoose/lib/schema.js:198:13
at complete (/media/linux/app/node_modules/mongoose/lib/document.js:1107:5)
at /media/linux/app/node_modules/mongoose/lib/document.js:1133:20
at ObjectId.SchemaType.doValidate (/media/linux/app/node_modules/mongoose/lib/schematype.js:645:22)
at /media/linux/app/node_modules/mongoose/lib/document.js:1129:9
at doNTCallback0 (node.js:407:9)
at process._tickCallback (node.js:336:13)
npm ERR! Linux 3.19.0-25-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v4.1.1
npm ERR! npm v2.14.4
npm ERR! code ELIFECYCLE
npm ERR! app#0.0.0 start: `node ./bin/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the app#0.0.0 start script 'node ./bin/www'.
npm ERR! This is most likely a problem with the bocerapp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./bin/www
npm ERR! You can get their info via:
npm ERR! npm owner ls app
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /media/linux/app/npm-debug.log
Thanks in advance!
I'm trying to install a nodejs application in heroku but can not be deployed, because node-gyp rebuild of the base64 library. Any idea to solve this deploy issue.
Works ok locally, the issue is only deploying into heroku. Any ideas to solve it?
Gizras-iMac:negawatt-iec-scraper gizra$ git push heroku master
Fetching repository, done.
Counting objects: 76, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (49/49), done.
Writing objects: 100% (49/49), 11.00 KiB | 0 bytes/s, done.
Total 49 (delta 37), reused 0 (delta 0)
-----> Fetching custom git buildpack... done
-----> Node.js app detected
PRO TIP: Specify a node version in package.json
See https://devcenter.heroku.com/articles/nodejs-support
-----> Defaulting to latest stable node: 0.10.33
-----> Downloading and installing node
-----> Restoring node_modules directory from cache
-----> Pruning cached dependencies not specified in package.json
-----> Node version changed since last build; rebuilding dependencies
> base64#2.1.0 install /tmp/build_fc23248efe5a35c5b79d9762e3733365/node_modules/base64
> node-gyp rebuild
make: Entering directory `/tmp/build_fc23248efe5a35c5b79d9762e3733365/node_modules/base64/build'
CXX(target) Release/obj.target/base64/base64.o
SOLINK_MODULE(target) Release/obj.target/base64.node
SOLINK_MODULE(target) Release/obj.target/base64.node: Finished
COPY Release/base64.node
ACTION binding_gyp_after_build_target_symlink /tmp/build_fc23248efe5a35c5b79d9762e3733365/node_modules/base64/base64.node
ln: creating symbolic link `/tmp/build_fc23248efe5a35c5b79d9762e3733365/node_modules/base64/base64.node': File exists
make: *** [/tmp/build_fc23248efe5a35c5b79d9762e3733365/node_modules/base64/base64.node] Error 1
make: Leaving directory `/tmp/build_fc23248efe5a35c5b79d9762e3733365/node_modules/base64/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/tmp/build_fc23248efe5a35c5b79d9762e3733365/vendor/node/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack at ChildProcess.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:810:12)
gyp ERR! System Linux 3.8.11-ec2
gyp ERR! command "node" "/tmp/build_fc23248efe5a35c5b79d9762e3733365/vendor/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /tmp/build_fc23248efe5a35c5b79d9762e3733365/node_modules/base64
gyp ERR! node -v v0.10.33
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm ERR! base64#2.1.0 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the base64#2.1.0 install script.
npm ERR! This is most likely a problem with the base64 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls base64
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.8.11-ec2
npm ERR! command "/tmp/build_fc23248efe5a35c5b79d9762e3733365/vendor/node/bin/node" "/tmp/build_fc23248efe5a35c5b79d9762e3733365/vendor/node/bin/npm" "rebuild"
npm ERR! cwd /tmp/build_fc23248efe5a35c5b79d9762e3733365
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /tmp/build_fc23248efe5a35c5b79d9762e3733365/npm-debug.log
npm ERR! not ok code 0
Old question but I ran into this and solved it via a few routes:
Failed at the base64#2.1.0 install script
Here the base64#2.1.0 might not be compatible with your version of node running your project. Try to install an earlier version.
Delete the ~/.node-gyp folder on your computer (command spacebar and search for ~/.node-gyp) and try reinstalling node-gyp globally.