Fatal error: spawn ENOENT node.js and grunt - node.js

Hi for responsive images i downloaded project from
https://github.com/andismith/grunt-responsive-images
i installed all those things what they have mentioned...
whenever i say grunt it saying fallowing error:
Running "jshint:all" (jshint) task
>> 3 files lint free.
Running "clean:tests" (clean) task
Cleaning "tmp"...OK
Running "responsive_images:default_options" (responsive_images) task
Fatal error: spawn ENOENT
why i am getting this error pla tellme...
Thnk you.

It is likely because you don't have imagemagick installed: http://www.imagemagick.org/script/index.php
See the FAQ on that plugin: https://github.com/andismith/grunt-responsive-images#faq

I experienced exactly the same error as you yesterday, and I found that I had installed wrong version of node.js eventually.
I'm using 64-bit Windows,but I had installed 32bit version Node.js.
I could install it and it seems working normally, but when I tried to compile existing project, the error message had been shown.
But after I re-install 64-bit version of Node.js, all error had been solved.
If you are using 64bit OS, better to check the version is correct or not.

Related

How to solve "plugin failed code 127" compiling with nanopb

I am trying to compile a c++ code in an conan enviroment, here are details:
Ubuntu 18.04 WSL x86-64
Windowns 10 x64
python 3.7.5
protoc 3.19.4
The project is located at /mnt/c/project
The build directory is located at /mnt/c/build
The build occurs without any errors but when I try to compile with "ninja" it throws an error related to protoc-gen-nanopb, as you can see attached image.
I tried to install a new protobuf from its c++ source, i added the LD_LIBRARY_PATH that was missing, and I have also tried to clean everything and erase all the files and build again. Everything seems to fail. I believe it's related to compatibility between protobuf and my python version, but I am not sure.
Could someone help me understand how to solve it? I am new to ubuntu and stackoverflow and i am sorry if some information is missing. In this case, just ask.
Error 127

Installing Sails leads to Link.exe error in windows

I'm trying to install Sails.JS 0.11.0 to my Windows 7 laptop (intel cpu) but receive an error when npm tries to build it. The error is pasted at the end of this message.
I'm using Node 0.10.38 (required for my use of the OracleDB module, so I can't upgrade to version 12 yet).
My laptop has Visual Studio 2013 Express Desktop which is used to compile.
The Sails npm install completes using npm -g list sails, but with errors, so I worry it's not properly installed.
So far, I've reboot my computer, wiped its temp files, and did everything I can think of. Any suggestions? I can't find any compatibility info on the Sails site (maybe I need to install an older version of Sails?).
The link-cvtres.write.[ID].tlog file referenced below seems to exist in that directory (which is built on the fly)... at least, a version of the file with a "1" in place of the "[ID]" is there.
Any help is appreciated.
Error Message (in the red output):
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(607,5): error MSB6003: The specified task executable "link.exe" could not be run. C:\Users\me\AppData\Roaming
\npm\node_modules\sails\node_modules\sails-hook-sockets\node_modules\socket.io\node_modules\socket.io-client\node_modules\engine.io-client\node_modules\ws\build\Release\obj\validation\validation.tlo
g\link-cvtres.write.[ID].tlog [C:\Users\me\AppData\Roaming\npm\node_modules\sails\node_modules\sails-hook-sockets\node_modules\socket.io\node_modules\socket.io-client\node_modules\engine.io-cl
ient\node_modules\ws\build\validation.vcxproj]`

Fatal errors when building Knockout.js

Running a totally fresh instance of Ubuntu 13.10 x64 on DigitalOcean. Every time I try and build Knockout.js using npm/grunt I get the following error:
Running "clean" task
Running "checktrailingspaces:main" (checktrailingspaces) task
Running "build:debug" (build) task
Running "build:min" (build) task
Compiling...Fatal error: spawn ENOENT
The strange part is, the Fatal error is seemingly random. It is always one of these three:
Fatal error: spawn ENOENT
Fatal error: spawn EPIPE
Fatal error: spawn ECONNRESET
I can build everything successfully on Mac OS X as well as an instance of Ubuntu 13.10 x64 at Linode, as well as Ubuntu 13.10 x64 on my home machine. I spun up several instances of Ubuntu 13.10 on different hosts and could only reproduce it on DigitalOcean.
I'm thinking something is funky with DigitalOcean's Ubuntu images, but do not know enough to say for sure. I could be missing some prerequisite packages, but I read all the docs and made sure I met all the requirements for Node/npm/grunt.
I have contacted DigitalOcean and got some great support. An employee managed to reproduce my errors but did not find a solution.
Any help is appreciated greatly.
Edit: My issue was solved below, and had absolutely nothing to do with DigitalOcean's images.
Fatal error: spawn ENOENT means child_process.spawn in node.js cannot find the binary you're attempting to spawn.
So likely you have some dependency the library requires installed on your OSX machine but not on the Ubuntu machine.
Look into your build task to see where and what it is trying to spawn. Running grunt with grunt --stack should help.

nodejs: node-gyp rebuild - Access is denied

I am trying to install nodetime module to profile my nodejs app..
When i run > npm install nodetime
the files are downloaded. but when node-gyp rebuild runs.
I get the following error.
Command failed: CreateProcessW: Access is denied
The same thing happens, when i try to download v8-profiler.
Nodejs ver: 0.8.15
node-gyp: 0.7.1
I have tried this on both my dev machine that runs window 7 and on windows server 2008 where this app will be hosted..
Any help is appreciated. Please let me know if more explanation is required
Update:
Sorry I had ignored this post for a while.. Had a chat with someone I assume is the author of nodetime and here are the things required for nodetime to run on Windows.
Python version 2.7
If on windows the PATH environment variable for python should include python.exe Eg: C:\Python27\Python.exe
It requires CPP compilers that come with Visual C++ Express edition and Windows 7 64-bit SDK (SDK compiler is required for 64-bit version of nodejs).
Hope this helps.
Try just set PATH=C:\Python27;%PATH%
DO NOT set PYTHON variable (check that its not set on your machine).
I had incorrectly set the PYTHON variable some time ago - which then caused me this headache for ages until I managed to figure out what was wrong.

Problem installing sqlite3-ruby on cygwin

I'm getting error while trying to install sqlite3-ruby gem:
gem install sqlite3-ruby-1.3.1.gem
Building native extensions. This could take a while...
ERROR: Error installing sqlite3-ruby-1.3.1.gem:
ERROR: Failed to build gem native extension.
/usr/bin/ruby.exe extconf.rb
Gem files will remain installed in /usr/lib/ruby/gems/1.9.1/gems/sqlite3-ruby-1.3.1 for inspection.
Results logged to /usr/lib/ruby/gems/1.9.1/gems/sqlite3-ruby-1.3.1/ext/sqlite3/gem_make.out
Same using:
gem install sqlite3-ruby-1.3.1
And that worked:
gem install sqlite3-ruby-1.3.1-x86-mswin32-60.gem
However I discovered I had had installed sqlite-ruby-1.2.5
Well my question is how 'gem' is installing these things? Why it can't choose sqlite3-ruby-1.3.1-x86-mswin32-60.gem version automatically. Does 'gem' is aware of running on linux or windows? What is native extension for it and why it is failing to install predownloaded sqlite3-ruby-1.3.1.gem
Thanks in advance
Lots of people seem to be having this issue. I'm surprised this doesn't work out of the box, as I would have guessed cygwin+ruby+sqlite is a supercommon configuration. Anyway. Many people concentrate on sqlite3.h, which is what appears are missing in the error output. However, my problem was that gcc wasn't installed correctly. Apparently gcc can fail to install correctly under cygwin. I fixed that and it was fine. Also, make sure you install libsql3-devel in cygwin.
I've been down this road before. I failed installing Ruby in Windows to work with Cygwin and I failed on Ubuntu.
What you do to save yourself the time and trouble is get a VM running with a Linux image (Fedora seemed to work well) and work with Ruby in that.

Resources