Node.js – Update Ionic in the existing project

angularjsbowerionic-frameworknode.jsupdates

I was excited to see the Release version of Ionic, but found myself unable to update my existing project. Here is what I did.

run npm install -g ionic
Open bower.json in your App's root folder (the one above www)

You will find something like this here:

 {
   "name": "MyAppName",
   "private": "true",
   "devDependencies": {
     "ionic": "driftyco/ionic-bower#xxxxxxxx"
   }
 }

Change it to this (basically by changing the last line:

 {
   "name": "MyAppName",
   "private": "true",
   "devDependencies": {
     "ionic": "driftyco/ionic-bower#1.0.0-rc.1"
   }
 }

Save the file
Go to command line and run this in your App Folder
```
 bower update
 ionic lib update
```
Run ionic lib to check the version number

Edit

This post relates to Windows OS, as I am using 64 bit Windows 7.

Best Answer

I also had a lot of problems to update an existing ionic project. This is what I did to solve the issue:

Remove bower.json from www/lib/ionic
Execute ionic lib update from the source project.

This action will ask for confirmation, just type yes and your project will be updated to the latest version.

Related Solutions

Node.js – How to update NodeJS and NPM to the next versions

See the docs for the update command:

npm update [-g] [<pkg>...]

This command will update all the packages listed to the latest version (specified by the tag config), respecting semver.

Additionally, see the documentation on Node.js and NPM installation and Upgrading NPM.

The following original answer is from the old FAQ that no longer exists, but should work for Linux and Mac:

How do I update npm?
npm install -g npm
Please note that this command will remove your current version of npm. Make sure to use sudo npm install -g npm if on a Mac.

You can also update all outdated local packages by doing npm update without any arguments, or global packages by doing npm update -g.

Occasionally, the version of npm will progress such that the current version cannot be properly installed with the version that you have installed already. (Consider, if there is ever a bug in the update command.) In those cases, you can do this:
curl https://www.npmjs.com/install.sh | sh

To update Node.js itself, I recommend you use nvm, the Node Version Manager.

Git – How to update or sync a forked repository on GitHub

In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

# Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

# Fetch all the branches of that remote into remote-tracking branches

git fetch upstream

# Make sure that you're on your master branch:

git checkout master

# Rewrite your master branch so that any commits of yours that
# aren't already in upstream/master are replayed on top of that
# other branch:

git rebase upstream/master

If you don't want to rewrite the history of your master branch, (for example because other people may have cloned it) then you should replace the last command with git merge upstream/master. However, for making further pull requests that are as clean as possible, it's probably better to rebase.

If you've rebased your branch onto upstream/master you may need to force the push in order to push it to your own forked repository on GitHub. You'd do that with:

git push -f origin master

You only need to use the -f the first time after you've rebased.

Edit

Best Answer

Related Solutions

Node.js – How to update NodeJS and NPM to the next versions

How do I update npm?

Git – How to update or sync a forked repository on GitHub

Related Topic