I've installed cordova via npm and i did it globally, now i would like to remove it to reinstall it on single app folder
Any clue on how to do it safely?
Try sudo npm uninstall cordova -g to uninstall it globally and then just npm install cordova without the -g flag after cding to the local app directory
Try this for Windows:
npm uninstall -g cordova
Try this for MAC:
sudo npm uninstall -g cordova
You can also add Cordova like this:
If You Want To install the previous version of Cordova through the Node Package Manager (npm):
npm install -g cordova#3.6.3-0.2.13
If You Want To install the latest version of Cordova:
npm install -g cordova
Enjoy!
Super late here and I still couldn't uninstall using sudo as the other answers suggest. What did it for me was checking where cordova was installed by running
which cordova
it will output something like this
/usr/local/bin/
then removing by
rm -rf /usr/local/bin/cordova
This can happen when the cordova was installed globally on a different version of the node.
Being necessary to manually delete yourself as suggested in the previous comment:
which cordova
it will output something like this
/usr/local/bin/
then removing by
rm -rf /usr/local/bin/cordova
worked for me:
which cordova
/opt/homebrew/bin/cordova
rm -rf /opt/homebrew/bin/cordova
Related
I'm trying to update my Ionic Cli from 6.12.2 to the latest version (6.19.0). I'm using Ubuntu. I was able to update node.js to the latest version, but when I run the commands:
npm uninstall -g ionic
npm uninstall -g #ionic/cli
with or without sudo command, when I run ionic -v again, it still say that I have the version 6.12.2 of ionic. and when I run npm install -g #ionic/cli and then run ionic -v it still say the same. Those commands are not being able to remove ionic from my Ubuntu.
That is something like a cache folder on ubunt that I should delete from system, related with the ionic cli, or something like that? Because I was not able to do this following the documentation on website.
To work around the problem, you can install the latest version from tarball:
cd /tmp
wget https://registry.npmjs.org/#ionic/cli/-/cli-6.19.0.tgz
sudo npm -g install cli-6.19.0.tgz
I Reinstalled Node.js and Yarn. Now I am getting this error.
My environment information is:
Node: v8.12.0
NPM: 6.4.1
Yarn: 1.10.1
OS: Windows 10
PS C:\Users\mdbel\Desktop\Project\redux> npx create-react-app learnredux
Creating a new React app in C:\Users\mdbel\Desktop\Project\redux\learnredux.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...
yarn add v1.10.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/#xtuc/long/-/long-4.2.1.tgz: Request failed \"404 Not Found\"".
info If you think this is a bug, please open a bug report with the information provided in "C:\\Users\\mdbel\\Desktop\\Project\\redux\\learnredux\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Aborting installation.
yarnpkg add --exact react react-dom react-scripts --cwd C:\Users\mdbel\Desktop\Project\redux\learnredux has failed.
Deleting generated file... package.json
Deleting generated file... yarn.lock
Done.
Once you have cleaned the yarn cache by running:
yarn cache clean
then subsequent calls to:
npx create-react-app your-app
will work.
I had same issue and solved it by:
Installing latest version of node, npm and yarn.
npm install -g npm#latest
nvm install node
npm install -g yarn
nvm installs Node.js and npm manages packages.
I solved this problem by deleting .yarnrc file from C:\Users\yourUserName\
removing .npmrc from C:\Users\you\.npmrc can also solve the problem.
I had a same problem then i tried the below Command and it fixed my issue
npm cache clean --force
The above command didn't solved your problem then try the below one.
npm init -y
npx create-react-app your-app-name
updating to latest stable version of yarn and removing yarn cache folder in the AppData folder has solved my issue C:\Users\test\AppData\Local\Yarn
I faced the same issue when using npx and was able to resolve this with the following steps:
Upgraded to latest yarn version: $ npm i #yarn#latest
Remove node_modules folder
Remove yarn.lock (if it exists).
Remove .npmrc from your user folder.
If the issue still persist you can use yarn command instead : $ yarn create react-app learnredux
yarn create is available in Yarn 0.25+
I had the same error on my Mac.
I just re-downloaded the installer from the Node.js website. This should reinstall all the dependencies and make sure that all paths are valid.
https://nodejs.org/en/download/
This might help for Linux operating system
sudo npm install -g npm#latest
npm install node
npm init
npm install -g yarn
yarn cache clean
npx create-react-app my-app
I also resolved my issue by installing the latest version of node from
https://nodejs.org/en/download/
And then i run below command
npm install -g create-react-app
in the terminal
Followed by "create-react-app " or "create-react-app ." if you are already in the folder.
Try this!
npm install -g npm#latest
npm install node
npm install -g yarn
npx create-react-app appname
cd firstapp
yarn start
Update node modules to version 13.12.0 that works for me
https://nodejs.org/es/download/current/
Yes, I have the same issue and I am unable to solve but after uninstalling yarn and updating node with the latest version.
Also, make sure you have installed
npm i -g create-react-app
after updating the packages.
Clean the cache also to make it free from bugs this will definitely work
Best method for windows user is update your yarn
If you use npx and got error than update yarn then use npx
I have same error in windows 8.1 then I updated yarn and it solved my problem
Npm I yarn#latest
npx creat-react-app app name
I encountered the same problem. It seems that this occurs when npm and node installation is broken. However, sometimes clearing cache doesn't work. I had to not just uninstall but delete/purge all npm and node files on my system, and reinstall them back again.
Remove node and npm
sudo rm -rf /usr/local/lib/node_modules
sudo rm -rf ~/.npm
sudo apt remove --purge npm
sudo apt remove --purge node
sudo apt remove --purge nodejs
Check if npm and node are removed by running: which node and which npm
If you still see some folders, try removing them using:
sudo apt-get remove nodejs
sudo apt-get remove npm
Update system, just in case
sudo apt-get update
Install node and npm
sudo apt-get install nodejs
sudo apt-get install npm
Check installation
npm -v
node -v
Note: The steps here involve removing existing modules and putting them back again. I also had to manually uninstall nodejs using Programs and Features (for Windows).
I accidentally hid the .yarnrc file and that caused the problem.
Re-installing node to the latest version worked for me.
https://nodejs.org/en/download/
I had the same problem. Instead of yarn you can use npm to create the app. Just add the --use-npm flag so:
npx create-react-app app --use-npm
I've tried several times to uninstall my angular-cli in order to update it but even if I follow the instructions provided on github:
npm uninstall -g #angular/cli
npm cache clean
npm install -g #angular/cli#latest
When I check using the command ng --version I still get the old version :
angular-cli: 1.0.0-beta.26
node: 7.7.1
os: darwin x64
How can i fix this issue? Thanks
I have also faced the same issue in recent past for me I have do the following commands one by one in terminal.
sudo npm uninstall -g angular-cli
sudo npm cache clean
After this run
ng -v
If still get angular-cli version 1.0.0-beta.2x.x then run the following command
which ng
It will show the ng path. Go to the path and if it is linked with any file remove the same the link and actual ng file. In my case the link is in /usr/bin/ng and actual path of ng file is /lib/node_modules/#angular/cli/bin/ng.
sudo rm -rf /lib/node_modules/#angular/cli/bin/ng
sudo rm -rf /usr/bin/ng
Next you need to install #angular/cli using
sudo npm install -g #angular/cli
Close all the terminal and run ng -v and you are on. May be it will help someone. Thanks :)
If you are facing issue with angular/cli then use the following commands:
npm uninstall -g angular-cli to uninstall the angular/cli.
npm cache clean to clean your npm cache from app data folder under your username.
use npm cache verify to verify your cache whether it is corrupted or not.
use npm cache verify --force to clean your entire cache from your system.
Note:
You can also delete by the following the paths
C:\Users\"Your_syste_User_name"\AppData\Roaming\npm and C:\Users\"Your_syste_User_name"\AppData\Roaming\npm-cache
Then use the following command to install latest angular/cli version globally in your system.
npm install -g #angular/cli#latest
To get more information visit github angular-cli update.
Updating Angular CLI
https://github.com/angular/angular-cli#updating-angular-cli
If you're using Angular CLI 1.0.0-beta.28 or less, you need to uninstall angular-cli package first.
npm uninstall -g angular-cli
npm uninstall -g #angular/cli
npm cache clean
npm install -g #angular/cli#latest
Then when it gets done successfully you may try:
ng --version
This sometime happens when you had actually installed #angular/cli using yarn and not npm.
You can verify this by looking in to yarn's global install folder.
You can remove it from yarn using
yarn global remove #angular/cli
You are using the beta version of angular CLI you can do this way.
npm uninstall -g #angular/cli
npm uninstall -g angular/cli
Then type,
npm cache clean
Then go to the AppData folder which is hidden in your users and go to roaming folder which is inside AppData then go to npm folder and delete angular files in there and also go to npm-cache folder and delete angular components in there.After that restart your PC and type
npm install -g #angular/cli#latest
This worked for me ✌️
I found a solution, first, delete the ng file with
sudo rm /usr/bin/ng
then install nvm (you need to restart your terminal to use nvm).
then install and use node 6 via nvm
nvm install 6
nvm use 6
finally install angular cli
npm install -g #angular/cli
this worked for me, I wanted to update to v1.0 stable from 1.0.28 beta, but couldn't uninstall the beta version (same situation that you desrcibed).
Hope this works
The following approach worked for me:
npm uninstall -g #angular/cli
and
npm cache verify
I had the same problem. This doesn't work:
npm uninstall -g angular/cli
npm cache clean
instead use:
npm uninstall -g # angular/cli
I could not get the angular-cli to go away. I FINALLY figured out a way to find it on my windows machine. If you have Cygwin installed or you are running linux or mac you can run which ng and it will give you the directory the command is running from. In my case it was running from /c/Users/myuser/AppData/Roaming/npm/ng
I had angular-cli version 1.0.0-beta.28.3, and the only thing that worked for me was deleting the angular-cli directly from the global node_modules folder:
cd /usr/local/bin/lib/node_modules
rm -rf angular-cli
After that ng version output was, as expected:
command not found: ng
And I could install the latest angular-cli version:
npm install -g #angular/cli#latest
Hope it helps...
Step 1:
npm uninstall -g angular-cli
Step 2:
npm cache clean
Step 3:
npm cache verify
Step 4:
npm cache verify --force
Note:
You can also delete by the following the paths
C:\Users"System_name"\AppData\Roaming\npm and
C:\Users"System_name"\AppData\Roaming\npm-cache
Then
Step 5:
npm install -g #angular/cli#latest
You have to use (without #)
npm uninstall -g angular/cli
because
If you're using Angular CLI beta.28 or less, you need to uninstall angular-cli package. It should be done due to changing of package's name and scope from angular-cli to #angular/cli https://github.com/angular/angular-cli
Try to update via these steps found in the npm repo for the angular cli.
npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli#latest
There is also an angular cli migration guide. One other option (more involved) is to start a new project and migrate over by copying and pasting certain files. This can be found here in the "moving into the cli" section of the angular-cli github
Check if you have the hidden folder ".npm" in your Home directory and delete the old angular-cli folder.
While uninstalling Angular CLI I got the same message (as it had some permission issues):
Unable to delete .Staging folder
I tried deleting the .staging folder manually, but still got the same error. I logged in from my administrator account and tried deleting the staging folder again manually, but to no avail.
I tried this (run as Administrator):
npm uninstall -g #angular/cli
npm cache verify
npm install -g #angular/cli.
Then I tried creating the project from my normal user account and it worked.
For those using Windows, I had this issue because :
after running npm uninstall -g # angular/cli, the folder AppData\Roaming\npm were still containing a ng file
this file prevented a complete uninstall of the CLI
I tried then to remove the ng file manually, but for some reasons it was not possible (I did not have the right), even as admin.
The only hack I found was using a 'linux based' command (I used Git bash) as admin and removing this file from command line:
cd AppData/Roaming/npm
rm ng.cmd
For information: this was with the version 6 of the CLI. There is not problem anymore to remove manually this specific file after the update.
I am facing an error while installing cordova and ionic each and everytime. As I start my installation using npm install -g cordova ionic. The installation cursor keeps on rotating like for many minutes and then I have to explicitly terminate the installation. Please help me with this issue.
you can try
npm --loglevel info install -g cordova ionic
and it should tell you more about what is happening / where the installation process stalls.
try npm install -g cordova first followed by npm install -g ionic
also you may need to install other missing components if any, CLI will intimate you very nicely.
What the command:
npm install -g cordova
ionic does is tries to install the cordova and ionic in a sequential order and -g manages the environment variables as well.
So, i recommend you to first install cordova then ionic.
npm install -g cordova,
npm install -g ionic,
Furthermore, i prefer using gitbash CLI rather than the cli provided by default.
It handles the issues of bower installation which may appear afterwards.And if you want a complete guide from installing to building an android project you can try the steps of the blog from here.
Good Luck.
Using cache help me to face this issue with following command :
npm install -g cordova ionic --cache "c:\path\to\use\as\dependencies\cache"
I had a makeshift setup on Lubuntu that 'functioned' with sudo npm install. I used Ionic Framework generator to create projects and they functioned as well as the builds and deployment.
I upgraded to 15.04 and ever since had problems finding a solution that worked does not give EACCESS errors or grunt serve telling me
Upgrade warning - for the CLI to run correctly,
it is highly suggested to upgrade the following:
Please update your Node runtime to version >=0.12.x
Please update your Cordova CLI to version >=4.2.0 npm install -g cordova
then for npm install -g cordova to tell me
npm WARN engine cordova-serve#0.1.3: wanted: {"node":">= 0.12.0","npm":">= 2.5.1"} (current: {"node":"0.10.26","npm":"2.12.1"})
I have tried the "chown -R whoami /dir/of/npm"
I have delete npm, node install brew and created new installs for all.
I still get EACCESS errors, my yo ionic "grunt serve" deploys the browser but gives ERR_CONNECTION_REFUSED
I installed brew, manually deleted the npm folder and did a clean install. No joy
which node - /home/username/.nvm/v0.10.26/bin/node
node -v v0.10.26
which npm - /home/userna/.linuxbrew/bin/npm
npm -v 2.12.1
which cordova - /usr/local/bin/cordova
cordova -v 3.5.0-0.2.6
And for good meassure i thought if i installed node4 all my troubles would disappear.
I know i messed this up but i would like a clean start with node, npm(without sudo) and cordova. Any help would be appreciated
Ps: I have done most of the normal suggestions hence my question.
Did you installed node using nvm?
So try
nvm use 4.0.0
In general:
nvm install [VERSION]
nvm use [VERSION]
To use permanent:
nvm alias default [VERSION]
try also to install cordova again after updating node
npm install -g cordova
If all fails:
Uninstall node and reinstall propper using brew:
cd ~
sudo rm -rf .npm
brew update
brew uninstall npm
brew install npm