I Can't uninstall my Appium by using npm
npm uninstall -g appium
or update by
npm install -g appium#1.19.1
Those commands still make the same result, That my Appium still be the old version.
How can I specify, Which path that my Appium has been installed ?
How I can update it ?
This is not Appium question, but node/npm one
npm root -g will show you the path to globally installed modules:
npm rm -g appium should delete the package completely
you may also what to clear cache npm cache clear
Related
functions: Cannot start emulator. Error: Cannot find module '#google-cloud/functions-emulator/src/config'
This is the error message I get when I try to run functions locally on Mac. My Firebase version is 3.16.0. I tried doing sudo npm install -g #google-cloud/functions-emulator as well. But still no use. Please help.
Solution is:
yarn global add firebase-tools
yarn global add #google-cloud/functions-emulator --ignore-engines
Working Solution!(OSX) None of the above worked for me. After a long struggle, I found the following solution.
cd my_project/functions
npm install #google-cloud/functions-emulator
Copy #google-cloud/functions-emulator folder generated inside node_modules.
cd /usr/local/lib/node_modules/#google-cloud && open .
Paste the functions-emulator folder here.
In your project's root directory, copy package.json inside functions/node_modules/#google-cloud/functions-emulator
cd /usr/local/lib && open .
Paste the package.json here.
npm install
Hurray! You are good to go. Now go back to your project's root directory and run.
sudo firebase serve --only hosting,functions
And the emulator should start normally.
Note: Do not run sudo npm install -g #google-cloud/functions-emulator since the files will be removed and reinstalled. This is where the installation fails and emulator fails to run.
Hope this helps!
The following worked for me.
npm uninstall -g firebase-tools && npm i -g firebase-tools
npm i --save #google-cloud/firestore
npm i --save #google-cloud/common-grpc
npm i -g #google-cloud/functions-emulator
npm i --save firebase-functions
current package.json snippet
"dependencies": {
"#google-cloud/common-grpc": "^0.5.3",
"#google-cloud/firestore": "^0.11.1",
"firebase-functions": "^0.8.1",
"firebase-admin": "5.8.1"
}
My system: Ubuntu 16.04.3
I had the same problem and the reason is that "#google-cloud/functions-emulator" is not installed in the 'npm global packages folder'.
In my case it happened because I installed firebase-tools globally using yarn, and I used it because when installing firebase-tools globally using npm I was getting an folder access error, which did not happen with yarn.
What I did to solve the problem was to follow these simple instruction from npm website to use a different folder for npm global packages (https://docs.npmjs.com/getting-started/fixing-npm-permissions).
Then I installed again with 'npm install -g firebase-tools' (without sudo) and it worked perfectly.
I had the same problem, using Ubuntu 17.10.
Note: You do not need to, and should not, use sudo for the installation.
I resolved this by performing the following:
Uninstall any previously attempted installed of the functions emulator.
npm uninstall -g #google-cloud/functions-emulator
and to make sure:
yarn global remove #google-cloud/functions-emulator
Delete all files in ~/.config/configstore/#google-cloud/functions-emulator. Note that there are some hidden files in this directory.
rm -rf ~/.config/configstore/#google-cloud/functions-emulator
Install nvm (node version manager) by following the instructions here:
https://github.com/creationix/nvm#install-script
Use nvm to install a specific version of node - at the time of writing, the Google Cloud Function Emulator (version 1.0.0-alpha.29) specifically requires 6.11.5.
nvm install 6.11.5
Install the Google Cloud Platform SDK:
https://cloud.google.com/sdk/
Reinstall the functions emulator:
npm install -g #google-cloud/functions-emulator
Start the emulator to verify installation has succeeded:
functions start
IMPORTANT: Subsequently, when attempting to create a function that can be tested locally or deployed to Google Cloud, you should use the firebase init functions command within your project, and allow this to install dependencies via npm. A walkthrough of creating a test function with Firebase can be found here:
https://firebase.google.com/docs/functions/get-started
i am windows user and trying to update firebase version using
npm install -g firebase-tools but when i run firebase --version
it shows the same version.
I also run npm uninstall firebase --save and check firebase --version it shows same.
what should i do to update my firebase version?
npm update -g firebase-tools
or
npm install -g firebase-tools#3.12.0 to install a specific version
And make sure to restart your terminal/IDE otherwise, it won't take effect.
Have you tried npm update -g firebase-tools? This worked for me.
These days if you're on an older version, and you check the version of firebase-tools, by running:
firebase -V
along with the version of firebase-tools that you're on, it also gives you a messages, something like this:
So you can basically run npm i -g firebase-tools to update the version of your firebase-tools installation to the latest version.
Hope this helps :)
For other like me stumbling in with a weird version mismatch:
When I did firebase -V in my terminal I would get a different version (5.1.1) than when I ran firebase through a npm run script (3.19.3)
The problem was that I had previously installed firebase locally into that project. In other words, I was getting the global version in the terminal, but npm was using the node_modules version
To confirm this, I added a simple test called test-foo to my package.json (firebase -V && which firebase) and ran it:
kuzyn(λ)matebox‡ npm run test-foo
kuzyn-project#1.1.0 test-foo /home/kuzyn/code/kuzyn-project/firebase
firebase -V && which firebase
3.19.3
/home/kuzyn/code/kuzyn-project/firebase/node_modules/.bin/firebase
Then I removed the (uneeded in my case) local firebase package from the package.json and from node_modules
Try the 2 steps bellow
1. yarn/npm cache clean
2. npm install -g firebase firebase-tools or yarn add -g firebase firebase-tools
in a new terminal, firebse --version
works for me
it works to me...
standalone binary: Download the new version, then replace it on your system
if you are using the standalone.Download the new version
In my case I was using an old node version (v10) and had to switch to a newer one (v12). After that I ran npm install -g firebase-tools again and it was updated to the latest version.
You can check the current node version by running node -v. And I use nvm to switch to a different node version.
That might happen in case you've installed the firebase-cli using a so called automatic install script.
Try to call curl -sL https://firebase.tools | upgrade=true bash as described in the official documentation
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
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'm on Windows and installed the new grunt using:
npm install -g grunt-cli
npm install -g grunt-init
grunt-init is the issue here.
If I try to run "grunt-init" in the command console, it is not recognised. Also after restarting the PC it's a nogo.
I checked the environment settings and grunt-init is indeed not included. In fact, when checking the node_modules directory (in "C:\Users\\AppData\Roaming\npm\node_modules") I see a directory "grunt-init", but there is no .cmd or other executable whatsoever.
Before I file a bug I wanted to ask here, because it seems that other Windows users have no issues with this..
Apparently version 0.1.0, the version that will be installed by a regular npm install -g grunt-init is not added to the PATH, because it has no bin directory. If you install the lates version (currently 0.2.0rc3) it should work as expected. Therefor run:
npm install -g grunt-init#0.2.0rc3
At least on Mac it works, but I think it works out on Windows too
FIRST make sure that you do:
npm uninstall -g grunt-init
Double check the following folders to ensure that grunt-init is gone:
[%USERNAME%]\AppData\Roaming\npm
[%USERNAME%]\AppData\Roaming\npm\node_modules
[%USERNAME%]\AppData\Roaming\npm-cache
After this is done, then as #marcello mentioned you should install current version of grunt-init (as of this writing):
npm install -g grunt-init#0.2.0rc3