I install firebase-tools with npm
but terminal can't find firebase-tools :(...
also I tried auto installing script "curl -sL https://firebase.tools | bash" but this also give me this error "This tool has encountered an error."
what should i do?
KangTaeui-MacBook-Pro-2:practice_react kangtaegeun$ sudo npm install firebase-tools -g
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
/Users/kangtaegeun/.npm-global/bin/firebase -> /Users/kangtaegeun/.npm-global/lib/node_modules/firebase-tools/lib/bin/firebase.js
> protobufjs#6.10.1 postinstall /Users/kangtaegeun/.npm-global/lib/node_modules/firebase-tools/node_modules/protobufjs
> node scripts/postinstall
+ firebase-tools#8.9.0
added 593 packages from 364 contributors in 32.084s
KangTaeui-MacBook-Pro-2:practice_react kangtaegeun$ firebase
-bash: /usr/local/bin/firebase: No such file or directory
KangTaeui-MacBook-Pro-2:practice_react kangtaegeun$
fangyongteng$ cnpm install -g ios-deploy Downloading ios-deploy to
/usr/local/lib/node_modules/ios-deploy_tmp Copying
/usr/local/lib/node_modules/ios-deploy_tmp/_ios-deploy#1.9.2#ios-deploy
to /usr/local/lib/node_modules/ios-deploy Installing ios-deploy's
dependencies to /usr/local/lib/node_modules/ios-deploy/node_modules
scripts.preinstall ios-deploy#1.9.2 "./src/scripts/check_reqs.js &&
xcodebuild" stderr: xcode-select: error: tool 'xcodebuild' requires
Xcode, but active
developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
Install fail! Error: Run "sh -c ./src/scripts/check_reqs.js &&
xcodebuild" error, exit code 1
Error: Run "sh -c ./src/scripts/check_reqs.js && xcodebuild" error,
exit code 1
at ChildProcess.proc.on.code (/usr/local/lib/node_modules/cnpm/node_modules/runscript/index.js:74:21)
at ChildProcess.emit (events.js:159:13)
at maybeClose (internal/child_process.js:943:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5) npminstall version: 3.3.0 npminstall
args: /usr/local/Cellar/node/9.3.0_1/bin/node
/usr/local/lib/node_modules/cnpm/node_modules/npminstall/bin/install.js
--china --userconfig=/Users/fangyongteng/.cnpmrc --disturl=https://npm.taobao.org/mirrors/node --registry=http://registry.npm.taobao.org -g ios-deploy
I also have the same problem, and my solution is use sudo xcode-select --reset
I carried out this statement solves this problem: sudo xcode - select - switch/Applications/Xcode9.2 app/Contents/Developer
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)
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 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