We Keep Coding

Fatal error LNK1181 when trying to npm install web3

I am trying to install the web3 node package with npm install. I am aware of the fact that I first need to install Windows build tools since I am running windows:
npm install --global --production windows-build-tools
This command goes through fine but when I run the command to install web3 I get the following error:
npm WARN deprecated fs-promise#2.0.3: Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated tar.gz#1.0.7: ⚠️ WARNING ⚠️ tar.gz module has been deprecated and your application is vulnerable. Please use tar module instead: https://npmjs.com/tar
> scrypt#6.0.3 preinstall [project path]\node_modules\scrypt
> node node-scrypt-preinstall.js
> scrypt#6.0.3 install [project path]\node_modules\scrypt
> node-gyp rebuild
[project path]\node_modules\scrypt>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Warning: Missing input files:
[project path]\node_modules\scrypt\build\..\scrypt\win\include\config.h
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
Copying scrypt/win/include/config.h to scrypt/scrypt-1.2.0/config.h
The system cannot find the file specified.
win_delay_load_hook.cc
LINK : fatal error LNK1181: cannot open input file '[user path]\.node-gyp\9.8.0\x64\node.lib' [[project path]\node_modules\scrypt\build\copied_files.vcxproj]
memlimit.c
keyderivation.c
pickparams.c
hash.c
win_delay_load_hook.cc
scrypt_wrapper.vcxproj -> [project path]\node_modules\scrypt\build\Release\\scrypt_wrapper.lib
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:258:23)
gyp ERR! stack at ChildProcess.emit (events.js:180:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12)
gyp ERR! System Windows_NT 10.0.16299
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 [project path]\node_modules\scrypt
gyp ERR! node -v v9.8.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN inbox#1.0.0 No description
npm WARN inbox#1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.1.3 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! scrypt#6.0.3 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the scrypt#6.0.3 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! [user path]\AppData\Roaming\npm-cache\_logs\2018-03-16T15_29_59_737Z-debug.log
After some additional research about why this happens I found out that the error pops up when the install process tries to install scrypt (?).
What is the problem? I have also added the environment variables for python that are required after the Windows build tools setup.

To resolve this error, use the path, with no spaces, or quotation marks in the path of the project properties.

Ouch so sorry 'cause i can't see what's happening and why it's not working...
I've tryed and it's worked for me with this method :
npm install --global --production windows-build-tools
npm install --save web3#1.0.0-beta.26
And web 3 V 1.0 is correctly installed.
If someone else can help ;)

Running as root or Administrator can fix the problem.
I had the same error. I followed Azerus's advice and created new path with only Latin letters and no spaces (actually I just created new user and logged in). But it still did not work but the error number was different. And then I got the idea to run cmd as Administrator and... it's done.

Cannot install electron in Ubuntu

My npm version is 3.10.10
And node version is v7.2.1
And when I tried to install electron in ubuntu via :
sudo npm install electron --save-dev
I get error like this :
Error: read ECONNRESET
at exports._errnoException (util.js:1022:11)
at TLSWrap.onread (net.js:572:26)
npm WARN enoent ENOENT: no such file or directory, open '/home/dotmark/package.json'
npm WARN dotmark No description
npm WARN dotmark No repository field.
npm WARN dotmark No README data
npm WARN dotmark No license field.
npm ERR! Linux 3.13.0-87-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "electron" "--save-dev"
npm ERR! node v7.2.1
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! electron#1.4.13 postinstall: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the electron#1.4.13 postinstall 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 electron 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 electron
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls electron
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/dotmark/npm-debug.log

You can't add a module to the dependencies of the package you are writing (--save-dev) unless you first create a package (with npm init or by manually writing a package.json).
… but don't make the root of your package your own home directory. Create a directory for it.

Command 'export' not recognized after 'npm run build' with webpack

We want to use webpack in our project. It has already been partly integrated as a test on a Mac and it works.
When using the same branch on my Windows machine I get following error message.
Webpack version ist 1.12.15
The part in German means that command 'export' could not be recognized or was not written correctly.
S:\project>npm run build
> project#version build S:\project
> export NODE_ENV=dev && webpack
Der Befehl "export" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\someone\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
npm ERR! node v4.4.1
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! project#version build: `export NODE_ENV=dev && webpack`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the project#version build script 'export NODE_ENV=dev && webpack'.
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 onedata package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! export NODE_ENV=dev && webpack
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs project
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls project
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! S:\project\npm-debug.log
It is not possible to use the newest node.js, as some other packages are incompatible to it.

Can't run npm install without sudo. Setting permissions to .npm didn't work

Im running Ubuntu 14.04 and have installed nodejs from the ppa https://launchpad.net/~chris-lea/+archive/ubuntu/node.js. When ever I try to run npm install it gives an error like this : (running the command npm install -g generator-ember)
npm ERR! Error: EACCES, unlink '/usr/lib/node_modules/generator-ember'
npm ERR! { [Error: EACCES, unlink '/usr/lib/node_modules/generator-ember']
npm ERR! errno: 3,
npm ERR! code: 'EACCES',
npm ERR! path: '/usr/lib/node_modules/generator-ember' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! System Linux 3.13.0-37-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "-g" "generator-ember"
npm ERR! cwd /home/pubudu/Projects/techpro-yeoman
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! path /usr/lib/node_modules/generator-ember
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, unlink '/usr/lib/node_modules/generator-ember'
npm ERR! error rolling back Error: EACCES, unlink '/usr/lib/node_modules/generator-ember'
npm ERR! error rolling back { [Error: EACCES, unlink '/usr/lib/node_modules/generator-ember']
npm ERR! error rolling back errno: 3,
npm ERR! error rolling back code: 'EACCES',
npm ERR! error rolling back path: '/usr/lib/node_modules/generator-ember' }
npm ERR! not ok code 0
I tried setting the permissions like this : sudo chown -R yourusername ~/.npm but it didn't work. How can I fix this? I can run npm with sudo but if I do, later im running into permission problems like when using grunt.

I had manies an issue with this too.
Changing the ownership of ~/.npm isnt enough because you are also getting access issues in /usr/lib/node_modules/ folders. You can change permissions here too if you like but changing permissions on folders is not recommended. If you were to change permissions on these folders too only do it on the folder you need ie the node_modules folder. Or you could go a different, more preffered, route -
Originally I went in and changed permissions of folders and all of that jazz but when I upgraded my system I used NVM.
From the ember-cli page, the link below leads to a tutorial about how to use npm and nodejs without using sudo by using node version manager:
http://www.wenincode.com/installing-node-jsnpm-without-sudo/
Once you have installed nvm as the tutorial above or as the github page tells you then whenever you log into a new shell you just use the command:
nvm use 0.10
where 0.10 is the version of nodejs you want to use.

Installing Inotify with NPM

I'm quite new to nodeJS and I'm trying to install a package called inotify using the Node Package Manager (NPM).
After installing NPM (on OSX Lion), I tried to install inotify with the command:
sudo npm install inotify
And I get the following error:
npm http GET https://registry.npmjs.org/inotify
npm http 304 https://registry.npmjs.org/inotify
> inotify#0.2.2 install /usr/local/lib/node_modules/inotify
> node-waf configure build
Checking for program g++ or c++ : /usr/bin/g++
Checking for program cpp : /usr/bin/cpp
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for g++ : ok
Checking for node path : not found
Checking for node prefix : ok /usr/local/Cellar/node/0.6.6
Checking for program node : /usr/local/bin/node
Checking for function inotify_init : not found
/usr/local/lib/node_modules/inotify/src/wscript:11: error: the configuration failed (see '/usr/local/lib/node_modules/inotify/build/config.log')
npm ERR! error installing inotify#0.2.2
npm ERR! inotify#0.2.2 install: `node-waf configure build`
npm ERR! `sh "-c" "node-waf configure build"` failed with 1
npm ERR!
npm ERR! Failed at the inotify#0.2.2 install script.
npm ERR! This is most likely a problem with the inotify package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-waf configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls inotify
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Darwin 11.2.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "inotify"
npm ERR! cwd /Users/username/code
npm ERR! node -v v0.6.6
npm ERR! npm -v 1.1.4
npm ERR! code ELIFECYCLE
npm ERR! message inotify#0.2.2 install: `node-waf configure build`
npm ERR! message `sh "-c" "node-waf configure build"` failed with 1
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/username/code/npm-debug.log
npm not ok
Can someone help me out with this

The inotify module won't build because it can't find inotify_init. This is because inotify is not available on OS X.
The FSEvents API on OS X provides similar functionality, but it's a completely different API. The inotify module is not going to work in this situation.
Depending on what you are trying to do, fs.watch might suit your needs. It abstracts away platform differences:
On Linux systems, this uses inotify.
On BSD systems (including OS X), this uses kqueue.
On SunOS systems (including Solaris and SmartOS), this uses event ports.
On Windows systems, this feature depends on ReadDirectoryChangesW.