I see errors when i try to install iron-meteor
command - sudo -H install -g iron-meteor
> fibers@1.0.5 install /usr/lib/node_modules/iron-meteor/node_modules/fibers
> node ./build.js
child_process: customFds option is deprecated, use stdio instead.
gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node- gyp/0.12.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_modules/iron- meteor/node_modules/fibers/.node-gyp"
@lai I tried nvm last night , same issue . I wonder whats goin on . And to my amaze I dont see a proper installation method on node.js site …I am trying another method … update ya soon
Solved: This is how I did to make iron-meteor work on my ubuntu 14.04 LTS
Uninstalled node and npm which where previously installed cd into path and than rm -r bin/node bin/node-waf include/node lib/node lib/pkgconfig/nodejs.pc share/man/man1/node.1
Install Linuxbrew maintained by Homebrew. Follow the instructions here (Linuxbrew) http://brew.sh/linuxbrew/
You should not mix and match package managers and linuxbrew is not a package manager with a deep understanding of linux/ubuntu global package dependency tree.
Also deleting directories in the wild like that is a bad idea as well.
It may onle useful if you want to clean up a system from a bad manual install of node.
The proper way to install node and npm is to install them using node’s official ubuntu package repository. Here’s a link to the latest information
And remember to install v0.10 not v0.12 because that’s what meteor’s going to be running on if you ever want to try out adeployment with meteor build.
After installing node (which also installs npm) by those instructions, install global npm packages with
$sudo -H npm install -g packagename
The trick here is -H which tells ubuntu that you need elevated privileges to install files into global ubuntu directories but user related files should still go into the user’s home not root’s home so that when you actually run those packages they use your home folder for private information.
Regarding nvm, yes it is a good way to manage multiple node versions should you actually ever do node development other than meteor. If you develop only on meteor, and maybe just a little node then this is a good way to keep a clean and healthy system.
The proper way you mentioned didnt worked atall , by any means ,as I already tried them .
Nodejs nowhere mention How to uninstall … or atleast I couldnt figure out how to from their site.
And I didnt deleted the directories in wild , it was mentioned by some super users in stackoverflow.
Before ever reaching the Linux brew method , I have tried every single step mentioned anywhere on google , nothing helped .But yeah Linux brew did … and its working absolutely fine on my system without any trouble .
The -H thing . if you could visit my github issue page that I have mentioned , you would know I have already tried that , friend … Everytime and each time permission issues …
The link I’ve posted shows exactly how to install nodejs on ubuntu and
it is a link from the nodejs web site.
How did you install nodejs the first time?
Linuxbrew might have solved one specific issue for you this time, but
it is very likely that you’ll encounter more issues in the future.
I’d also take stackoverflow answers regarding files on a linux/unix
system with caution. Those answers are usually very case specific and repeating them
on your system, even when it looks like the same problem, may end up
bad for you.
@shail I do very sincerely care and would like this post to end up with a proper solution so that anyone who reads this in the future will know exactly what to do and what not to do.
I have also carefully read all of the posts in this thread, including the complete github issue you have originaly posted.
As I said, you have never mentioned how you installed node the first time you installed it on your computer.
You only mentioned trying to npm install the iron router package.
I am insisting on asking because the way you install node is 99% of the problems you have with npm install commands.
You see, if you had not installed node properly (I’m 99% sure that was the problem) according to the clear instructions given on nodejs web site, it is very normal to experience problems such as you have bumped into. And installing linuxbrew is the very last thing to do to mitigate such problems.
But before jumping to conclusions, I’d really like to know for 100% if that is the case or not. Thanks for keeping the discussion up.