I run the following command in my bash and I get the related results:
merianos#merianos-desktop:~$ sudo npm install -g grunt-cli
/usr/local/bin/grunt -> /usr/local/lib/node_modules/grunt-cli/bin/grunt
grunt-cli#0.1.13 /usr/local/lib/node_modules/grunt-cli
├── resolve#0.3.1
├── nopt#1.0.10 (abbrev#1.0.7)
└── findup-sync#0.1.3 (lodash#2.4.2, glob#3.2.11)
and
merianos#merianos-desktop:~$ grunt
/usr/bin/env: node: No such file or directory
I also have try to install bower and gulp but again, when I try to execute them, I get a message related to the grunt above.
Can someone please help me ?
Just to know, I just installed Ubuntu 15.04. I don't know if that helps :)
Ubuntu package nodejs provide a binary as a /usr/bin/nodejs, not a /usr/bin/node, so most of cli tools can't find it. To solve the problem you need to make a symlink:
sudo ln -sT /usr/bin/nodejs /usr/bin/node
Related
I have tried any ways I can but still can't install express successfully.
I used
sudo npm install -g express-generator
sudo npm install -g express
The terminal shows
/usr/bin/express -> /usr/lib/node_modules/express-generator/bin/express
express-generator#4.13.1 /usr/lib/node_modules/express-generator
├── sorted-object#1.0.0
├── commander#2.7.1 (graceful-readlink#1.0.1)
└── mkdirp#0.5.1 (minimist#0.0.8)
But when I input express, it still says "command not find". I also added the path"/usr/lib/node_modules/express-generator/bin" in system path, it still failed.
I stuck this problem for two days, it's quite annoying. Please help me.
Try $ sudo npm cache clean and then install express and express-generator without sudo.
Edit: Adding ~/npm/bin to path with PATH=$PATH:~/npm/bin helped, thank you Joachim Isaksson
EDIT:
Seems like i cannot install any packages with npm. After sucessfully installing them, i cannot use them with the assigned commands in the package. "No command '' found".
node -v
v0.11.14
npm -v
2.0.0
At ubuntu machine
It seems like i cannot install the resume-cli module, found here with using npm. Even though it installs without errors, it does not understand the basic commands after installing. Could it be a problem with the warning, showed under?
sudo npm install -g resume-cli
i get
npm WARN engine html-to-text#0.0.8: wanted: {"node":"~0.8.0"} (current: {"node":"0.10.32","npm":"1.4.28"})
Then
/home/bjornasm/npm/bin/resume -> /home/bjornasm/npm/lib/node_modules/resume-cli/index.js
resume-cli#0.3.10 /home/bjornasm/npm/lib/node_modules/resume-cli
├── cli-spinner#0.1.5
├── char-spinner#1.0.1
├── commander#2.3.0
├── colors#0.6.2
├── open#0.0.5
├── chalk#0.4.0 (has-color#0.1.7, ansi-styles#1.0.0, strip-ansi#0.1.1)
├── async#0.9.0
├── read#1.0.5 (mute-stream#0.0.4)
├── terminal-menu#0.3.2 (inherits#2.0.1, charm#0.1.2, resumer#0.0.0)
├── superagent#0.18.2 (extend#1.2.1, qs#0.6.6, methods#1.0.1, cookiejar#2.0.1, component-emitter#1.1.2, reduce-component#1.0.1, mime#1.2.11, debug#1.0.4, readable-stream#1.0.27-1, form-data#0.1.3, formidable#1.0.14)
├── resume-to-text#0.0.15 (mustache#0.8.2, html-to-text#0.0.8)
├── resume-to-html#0.0.21 (gravatar#1.0.6, resume-to-markdown#0.0.14, marked#0.3.2, mustache#0.8.2, lodash#2.4.1)
├── jsonlint#1.6.2 (nomnom#1.8.0, JSV#4.0.2)
└── resume-schema#0.0.15 (z-schema#2.4.10)
Then when running the following
resume --help
i get
resume: command not found
Anyone familiar with this?
Below are the steps to install a given release from source
NOTE - this installs nodejs which gives you both node as well as npm, they come together per release.
to start fresh remove prior node.js and npm installs as well as these :
sudo mv ~/.npmrc ~/.npmrc_ignore
sudo mv ~/.npm ~/.npm_ignore
sudo mv ~/tmp ~/tmp_ignore
sudo mv ~/.npm-init.js ~/.npm-init.js_ignore
to install nodejs and npm as yourself NOT root do these commands (OSX/linux) :
export NODE_PARENT=${HOME}/bin_0_10_32
mkdir ${NODE_PARENT}
download source from : http://nodejs.org/download/
cd node-v0.xxxx
./configure --prefix=${NODE_PARENT}/nodejs
make -j8
make install # IMPORTANT this is NOT using sudo
# not wanted since installing into $USER owned $NODE_PARENT
which puts it into dir defined by above --prefix
export PATH=${NODE_PARENT}/nodejs/bin:$PATH
define environment variable NODE_PATH so node can find dir for modules otherwise
npm install xxx will put newly installed module into current dir :
export NODE_PATH=${NODE_PARENT}/nodejs/lib/node_modules
when you use syntax : npm install -g some_cool_module
the -g for global installs it into dir $NODE_PATH and not your $PWD
nodejs install gives you npm as well :
ls -la ${NODE_PARENT}/nodejs/bin
Subsequent modules you install using global flag -g will automagically put their ~binaries~ into above bin dir ... like browserify
Now put above three export xxx=yyy
commands into your ~/.bashrc or some such so your environment is setup
I've ran into some problem with installing cordova and phonegap.
When i try to run sudo npm install -g cordova (same with phonegap). I got this result (for cordova)
/home/tomek/npm/bin/cordova -> /home/tomek/npm/lib/node_modules/cordova/bin/cordova
cordova#3.5.0-0.2.7 /home/tomek/npm/lib/node_modules/cordova
├── q#0.9.7
├── underscore#1.4.4
├── nopt#2.2.1 (abbrev#1.0.5)
└── cordova-lib#0.21.7 (osenv#0.0.3, properties-parser#0.2.3, bplist-parser#0.0.5, mime#1.2.11, semver#2.0.11, dep-graph#1.1.0, plist-with-patches#0.5.1, shelljs#0.1.4, xcode#0.6.6, npmconf#0.1.16, elementtree#0.1.5, glob#3.2.11, rc#0.3.0, tar#0.1.19, request#2.22.0, npm#1.3.4, cordova-js#3.6.2)
But when I later try to run cordova command it simply doesn't find this command.
What do I do wrong, and why it doesn't work?
You may have your nodes confused, try the following in terminal:
$ sudo ln -s /usr/bin/nodejs /usr/local/bin/node
This install guide may help you: http://software-issues.blogspot.co.uk/2014/04/v-behaviorurldefaultvmlo.html, with your distro being ubuntu based you should have no problem following this. (Beware I forgot to sudo the npm command in the guide, must get around to editing that).
I am trying to download and run PhoneGap. I have tried on 3 machines (2 mac, 1 windows), and I can't help but feel as though I am doing something wrong.
I have nodeJS (v0.10.13) and NPM (1.3.2) installed to the latest versions, using homebrew.
To install PhoneGap I do the following via commandline:
sudo npm install -g phonegap
NPM goes on it's merry way downloading a ton of packages and installing all without warning or error.
After install I get the following, which I assume is correct:
npm http 200 https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz
/usr/local/share/npm/bin/phonegap -> /usr/local/share/npm/lib/node_modules/phonegap/bin/phonegap.js
phonegap#3.0.0-0.14.0 /usr/local/share/npm/lib/node_modules/phonegap
├── pluralize#0.0.4
├── colors#0.6.0-1
├── semver#1.1.0
├── qrcode-terminal#0.9.4
├── shelljs#0.1.4
├── optimist#0.6.0 (wordwrap#0.0.2, minimist#0.0.1)
├── node-static#0.7.0 (colors#0.6.0, mime#1.2.9)
├── phonegap-build#0.8.3 (qrcode-terminal#0.8.0, optimist#0.3.7, shelljs#0.0.9, phonegap-build-api#0.3.3)
├── prompt#0.2.11 (revalidator#0.1.5, pkginfo#0.3.0, read#1.0.5, winston#0.6.2, utile#0.2.0)
└── cordova#3.0.0 (ncallbacks#1.0.0, colors#0.6.0, open#0.0.3, shelljs#0.1.2, follow-redirects#0.0.3, elementtree#0.1.3, glob#3.2.3, plist#0.4.3, prompt#0.2.7, xcode#0.5.1, tar#0.1.17, express#3.0.0, ripple-emulator#0.9.18, plugman#0.9.10, request#2.22.0)
MikeBook-Pro:apps Mike$
I then restart terminal (completely quit it, cmd+q) and run phonegap, to be greeted with:
MikeBook-Pro:~ Mike$ phonegap
-bash: phonegap: command not found
I'm at my wits end here. I've installed other stuff through NPM without a problem. My /etc/paths looks like the following:
/usr/bin
/bin
/usr/sbin
/sbin
/usr/local/bin
I have followed the above steps using cordova instead of phonegap, but alas; the same issue.
Any help is hugely appreciated, I just want to cry.
Edit: I'm currently trying this on OSX 10.8.2 (Mountain Lion)
I was some how missing a few paths from my /etc/paths file. Below is that new file:
/usr/bin
/bin
/usr/sbin
/sbin
/usr/local/bin
/usr/local/share
/usr/local/share/npm
/usr/local/share/npm/lib/node_modules/
/usr/local/share/npm/bin
.npm
I am having trouble running grunt-cli after installing it. I run
npm install -g grunt-cli
then running grunt errors with
node.js:63
throw e;
^
Error: Cannot find module 'findup-sync'
at loadModule (node.js:275:15)
at require (node.js:411:14)
at Object.<anonymous> (/home/tmartin/bin/grunt:9:14)
at Module._compile (node.js:462:23)
at Module._loadScriptSync (node.js:469:10)
at Module.loadSync (node.js:338:12)
at Object.runMain (node.js:522:24)
at Array.<anonymous> (node.js:756:12)
at EventEmitter._tickCallback (node.js:55:22)
at node.js:773:9
This is what I have installed:
tmartin#timcomp:~$ npm list -g
/home/tmartin/lib
└─┬ grunt-cli#0.1.6
├─┬ findup-sync#0.1.2
│ ├─┬ glob#3.1.21
│ │ ├── graceful-fs#1.2.0
│ │ ├── inherits#1.0.0
│ │ └─┬ minimatch#0.2.11
│ │ ├── lru-cache#2.2.2
│ │ └── sigmund#1.0.0
│ └── lodash#1.0.1
└─┬ nopt#1.0.10
└── abbrev#1.0.4
I had to install and link findup-sync and a few other npm packages to get these dependency issues to go away. I though npm was supposed to handle them for us, but installing the dependencies manually made the issues go away.
npm install findup-sync -g
npm link findup-sync
I got mine running again reinstalling grunt-cli globally and in my repo.
npm install -g grunt-cli
cd myrepo
npm install grunt-cli
I think Yosemite installation broke some things in my files ...
This is because npm doesn't set the right permission to sub-directory node_modules in /usr/lib/node_modules/grunt-cli.
In my case, I had:
drwxr-x--- 6 nobody root 4096 16 févr. 17:08 node_modules
When running grunt as non-root user, I had the same error (Cannot find module 'findup-sync') because of a permission denied to read this directory.
The solution is to fix permission with chmod: chmod a+rx node_modules.
But in fact, all directories was involved. The best way was to todo:
find /usr/lib/node_modules/grunt-cli -type d -exec chmod a+rx {} \;
This is maybe a distribution bug (I use Archlinux).
This may seem simple, but if anyone else is unsure if there's a permissions problem, try running sudo grunt then go from there.
I use NVM and was having this problem whenever I changed the active node version.
Following #davidcondrey 's suggestion worked for me. The catch really was to install grunt-cli before grunt. The order made a difference and fixed it.
npm i -g grunt-cli grunt
#inostia 's answer of using sudo to test the permissions was OK, but gave me quite a headache with file permissions, as all the grunt-processed files were inacessible by git later and broke my versioning.
This also may be obvious, but in my case I had set up my npm path off my home directory (on a chromebook) and needed to add .node_modules to my .profile
PATH=~./node_modules:$PATH
Then run:
source ~/.profile
I was able to fix this by reinstalling Grunt using these commands:
sudo npm remove -g grunt-cli
sudo npm install -g grunt-cli
This issue occurs if you change your NodeJS version.
After changing the node version, re installing grunt or npm install will resolve the issue.
Tried all the answers above and I could not get grunt to work without using sudo
Finally came across this Wordpress article and deleted the link to /usr/local/lib/node_modules/grunt/bin/grunt
lrwxrwxrwx 1 root root 35 Apr 19 22:45 /usr/local/bin/grunt -> ../lib/node_modules/grunt/bin/grunt
using sudo rm /usr/local/bin/grunt
Then I linked to the grunt executable in /usr/local/lib/node_modules/grunt-cli/bin
using sudo ln -s /usr/local/lib/node_modules/grunt-cli/bin/grunt /usr/local/bin/grunt
Now, I can run grunt without using sudo
I solved this by running:
npm install -gg grunt-cli --force