No matter what I try, every time I try to install polymer-cli, it always comes up with a PERMISSION_DENIED error.
bradley#gurulaptop:~$ sudo npm -g install polymer-cli
npm WARN deprecated bower#1.8.0: ..psst! While Bower is maintained, we recommend Yarn and Webpack for *new* front-end projects! Yarn's advantage is security and reliability, and Webpack's is support for both CommonJS and AMD projects. Currently there's no migration path but we hope you'll help us figure out one.
npm WARN deprecated #types/assert#0.0.29: See https://github.com/DefinitelyTyped/DefinitelyTyped/issues/12826
/usr/bin/polymer -> /usr/lib/node_modules/polymer-cli/bin/polymer.js
> wd#1.2.0 install /usr/lib/node_modules/polymer-cli/node_modules/wd
> node scripts/build-browser-scripts
/usr/lib/node_modules/polymer-cli/node_modules/mkdirp/index.js:90
throw err0;
^
Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/polymer-cli/node_modules/wd/build'
at Object.fs.mkdirSync (fs.js:877:18)
at sync (/usr/lib/node_modules/polymer-cli/node_modules/mkdirp/index.js:71:13)
at Object.<anonymous> (/usr/lib/node_modules/polymer-cli/node_modules/wd/scripts/build-browser-scripts.js:6:1)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Function.Module.runMain (module.js:605:10)
at startup (bootstrap_node.js:158:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! wd#1.2.0 install: `node scripts/build-browser-scripts`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the wd#1.2.0 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! /home/bradley/.npm/_logs/2017-06-06T13_10_23_400Z-debug.log
How can I solve this?
I faced the same problem and followed #Tim Lundqvist's answer and solved by the following way:
Step 1: Create a hidden folder in home. Commands:
$ cd ~
$ mkdir .polymer-patch
$ cd .polymer-patch
$ npm install polymer-cli
Step 2: create symbolic links to make it executables
$ sudo ln -s "$(readlink -f ~/.polymer-patch/node_modules/.bin/wd)" /usr/bin/wd
$ sudo ln -s "$(readlink -f ~/.polymer-patch/node_modules/.bin/polymer)" /usr/bin/polymer
$ polymer
Now polymer CLI is working for me.
Updated
This issue is node and npm version related but the following command works good
$ sudo npm install --unsafe-perm -g polymer-cli
There seems to be a problem installing the package wd as root. One way to work around this fact is to do a non global npm install of polymer-cli and use the local bin path.
$ cd ~
$ npm install polymer-cli
$ ~/node_modules/.bin/polymer --version
1.1.0
After which you may either copy all dependencies to /usr/lib/node_modules and /usr/bin/ or create symbolic links to the executables (which may be easier for a singe user system).
$ sudo ln -s "$(readlink -f ~/node_modules/.bin/wd)" /usr/bin/wd
$ sudo ln -s "$(readlink -f ~/node_modules/.bin/polymer)" /usr/bin/polymer
When the path /usr/bin/polymer exists you should be able to use the polymer command as expected.
I'm running Xubuntu, this worked
sudo npm install -g polymer-cli --unsafe-perm=true --allow-root
I got myself in the same situation. I could not install or update to the latest polymer-cli version (1.2.0). The two previous answers didn't help me at all. My solution was the downgrade of npm. I had installed:
node -v: v7.x.x
npm -v: v5.x.x
And that was the real problem.
After downgrading to npm 4.x.x by:
sudo npm install -g npm#4.1.2
I was able to install the latest polymer-cli via:
sudo npm install -g polymer-cli
Maybe you need previous also to uninstall the old wd & polymer-cli unifinished installation:
sudo npm uninstall -g wd polymer-cli
sudo rm /usr/bin/polymer
That work now for me with the tips of Tim and the same start bug after this clean up
Solved the issue: polymer-cli global install error
sudo npm install -g polymer-cli --unsafe-perm
I had the same problem, I tried different things, but what finally helped me was this:
sudo npm install -g yarn
(Consider Yarn and Webpack or Parce)
Related
When I try to run
$ grunt
it showing this error
Fatal error: unable to find local grunt
I have installed grunt in my project by using this command
npm install -g grunt-cli
can any one tell me what I have done wrong?
Try to use sudo as sometimes it is just because of access-permission issues. Also check if you are running the command in your project's root directory.
so try
sudo npm install -g grunt-cli
it might also be a good idea to update your update existing npm before installing grunt-cli by running
npm update -g npm
I am trying to develop ASP.NET applications using a macbook computer with the Yosemite operating system.
I've retrieved the DNVM using Homebrew with the following commands:
brew tap aspnet/dnx
brew update
brew install dnvm
I've also setup the ASP.NET generator using the following commands:
npm install -g yo generator-aspnet
npm install -g bower grunt-cli gulp-cli
At this point, everything should be ready to go. However, when I type yo aspnet in the terminal, it generates an error that states -bash: yo: command not found. What could be causing this and is there an easy fix?
I've referenced multiple resources, the two best listed below:
Reference_01: https://code.visualstudio.com/docs/aspnet5
Reference_02: http://tattoocoder.azurewebsites.net/vscode-creating-an-application-with-yeoman-aspnet-generators/
UPDATE
I made sure to install the following and it still won't recognize yo aspnet
node.js: brew install node
Yeoman: npm install -g yo
Install: npm install -g generator-aspnet
Run: yo aspnet
You need to change the permissions of your usr/local folders by running the following code:
sudo chown -R $USER /usr/local
sudo chown -R yourUsername ~/.npm
npm install -g yo grunt-cli bower
Once you have completed this step, reset the generator-aspnet by running the following lines of code:
npm install -g yo generator-aspnet
npm install -g bower grunt-cli gulp-cli
Now you should be able to run your executable line:
yo aspnet
I created a bundle and try install as wrote in readme
> node ./build.js
module.js:340
throw err;
^
Error: Cannot find module '/root/bundle/programs/server/node_modules/fibers/build.js'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3
npm ERR! fibers#1.0.1 install: `node ./build.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the fibers#1.0.1 install script.
npm ERR! This is most likely a problem with the fibers package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./build.js
npm install -g fiders works as well
I'm not sure if this is the same problem, but starting with 0.9.0 you have to install fibers after unpacking the build. From the readme:
To prepare a bundle created with meteor bundle for execution on a server, you now run npm install with no arguments instead of having to specify a few specific npm modules and their versions explicitly. See the README in the generated bundle for more details.
I do something like this in my deployment script:
meteor bundle /path/to/target/bundle.tgz
cd /path/to/target/
rm -rf bundle
tar xzf bundle.tgz
cd bundle/programs/server && npm install
When I try to install Sails.js, I get:
npm WARN deprecated grunt-lib-contrib#0.7.1: DEPRECATED. See readme: https://github.com/gruntjs/grunt-lib-contrib
npm WARN deprecated guid#0.0.12: Please use node-uuid instead. It is much better.
ws#0.4.32 install /usr/local/lib/node_modules/sails/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
(node-gyp rebuild 2> builderror.log) || (exit 0)
the console hangs right here and never does anything else.
I tried uninstalling all node_modules and reinstalling an earlier version:
sudo rm -rf node_modules
npm cache clear
sudo npm install npm#1.4.23 -g
sudo npm install sails -g
Still the exact same problem. Anyone else run into this and have a solution?
I had a similar problem. A better solution is to use:
npm -g install npm
This will install the latest npm version
A way of handling this, as I've seen it, is by installing the latest version of NPM:
npm install -g npm#1.4.24
And you may have to remove the Grunt Cli first done like so:
npm -g remove grunt-cli
The guys running Sails have also addressed this issue on GitHub: https://github.com/balderdashy/sails/issues/2124
I was using Mac OSX 10.7.5
I simply updated to 10.9.5 and followed the normal installation procedures, everything worked fine.
If you use apt-get or any other to install npm fist, then you must remove it with apt-get then use the sudo npm install -g npm#1.4.24 to install the 1.4 version
I need to know about install meteorite package in linux(Cent O.S) using Meteor.I'm try to using mrt & npm but i get errors like mrt not found and npm not found.I am new to meteor.So can you please suggest me how to use mrt and npm packages in Meteor?The below ones are using to install meteorite.
npm install -g meteorite
sudo -H npm install -g meteorite
The above both are get errors are npm is not found.
I'm using Ubuntu but get the below error :
[root#localhost HCare]# sudo apt-get install nodejs nodejs-dev npm
sudo: apt-get: command not found
[root#localhost HCare]#
The above both are get errors are npm is not found. And i'm using yum -y update and also get so many below messages but this is correct or not but i dont know?
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: PackageKit
Memory : 2.4 M RSS (356 MB VSZ)
Started: Sat Mar 22 06:41:50 2014 - 3 day(s) 12:13:19 ago
State : Sleeping, pid: 6457
and also does not exit and get a lot above messages.
I would suggest using the package manager for your distribution, in this case YUM:
Install nodejs and npm: yum install nodejs npm
Install meteorite npm install -g meteorite
Since you got meteor already installed, that's it.