<commit_before>---
layout: post
title: "Upgrading"
permalink: upgrading
github: "https://github.com/stefanpenner/ember-cli/blob/gh-pages/_posts/2013-04-03-upgrading.md"
---

### Upgrading an Ember CLI App

Steps to upgrade to the latest version of Ember CLI are included with [each
release](https://github.com/stefanpenner/ember-cli/releases), but these are the
common steps one would follow to update Ember CLI using NPM from within your
project directory.

#### Setup

* Remove old global ember-cli

    {% highlight bash %}
    npm uninstall -g ember-cli
    {% endhighlight %}

* Clear NPM cache

    {% highlight bash %}
    npm cache clean
    {% endhighlight %}

* Clear Bower cache

    {% highlight bash %}
    bower cache clean
    {% endhighlight %}

* Install a new global ember-cli, replacing X.X.X with the version of ember-cli
  you want to install

    {% highlight bash %}
    npm install -g ember-cli@X.X.X
    {% endhighlight %}

#### Project Update

* Delete temporary development folders

    {% highlight bash %}
    rm -rf node_modules bower_components dist tmp
    {% endhighlight %}

* Update your project's `package.json` file to use the latest version of
  ember-cli, replacing X.X.X with the version of ember-cli you want to install

    {% highlight bash %}
    ember install:npm ember-cli@X.X.X
    {% endhighlight %}

* Reinstall NPM and Bower dependencies

    {% highlight bash %}
    ember install
    {% endhighlight %}

* Run the new project blueprint on your projects directory. Please follow the
  prompts, and review all changes (tip: you can see a diff by pressing d).

    {% highlight bash %}
    ember init
    {% endhighlight %}

The most common sources of upgrade pain are not clearing out old packages in the
first step of the project update and missing a change in the last step of the
project update.  Please review each change from the last step carefully to
ensure you both have not missed a change from the upgrade and that you have not
accidentally removed code you may have added to your project during your work.

When the upgrade process has completed, you should be able to issue the `ember
-v` command and see that the `version:` noted in the resulting output matches
the version you just upgraded to.<commit_msg>Update 2013-04-03-upgrading.md<commit_after>---
layout: post
title: "Upgrading"
permalink: upgrading
github: "https://github.com/stefanpenner/ember-cli/blob/gh-pages/_posts/2013-04-03-upgrading.md"
---

### Upgrading an Ember CLI App

Steps to upgrade to the latest version of Ember CLI are included with [each
release](https://github.com/stefanpenner/ember-cli/releases), but these are the
common steps one would follow to update Ember CLI using NPM from within your
project directory.

#### Setup

* Remove old global ember-cli

    {% highlight bash %}
    npm uninstall -g ember-cli
    {% endhighlight %}

* Clear NPM cache

    {% highlight bash %}
    npm cache clean
    {% endhighlight %}

* Clear Bower cache

    {% highlight bash %}
    bower cache clean
    {% endhighlight %}

* Install a new global ember-cli, replacing X.X.X with the version of ember-cli
  you want to install

    {% highlight bash %}
    npm install -g ember-cli@X.X.X
    {% endhighlight %}

#### Project Update

* Delete temporary development folders

    {% highlight bash %}
    rm -rf node_modules bower_components dist tmp
    {% endhighlight %}

* Update your project's `package.json` file to use the latest version of
  ember-cli, replacing X.X.X with the version of ember-cli you want to install

    {% highlight bash %}
    npm install ember-cli@X.X.X --save-dev
    {% endhighlight %}

* Reinstall NPM and Bower dependencies

    {% highlight bash %}
    npm install
    bower install
    {% endhighlight %}

* Run the new project blueprint on your projects directory. Please follow the
  prompts, and review all changes (tip: you can see a diff by pressing d).

    {% highlight bash %}
    ember init
    {% endhighlight %}

The most common sources of upgrade pain are not clearing out old packages in the
first step of the project update and missing a change in the last step of the
project update.  Please review each change from the last step carefully to
ensure you both have not missed a change from the upgrade and that you have not
accidentally removed code you may have added to your project during your work.

When the upgrade process has completed, you should be able to issue the `ember
-v` command and see that the `version:` noted in the resulting output matches
the version you just upgraded to.
{'fraction_non_alphanumeric': 0.07732634338138926, 'fraction_numerical': 0.005242463958060288, 'mean_word_length': 3.3776290630975145, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1184109', 'n_tokens_mistral': 1397, 'n_tokens_neox': 1231, 'n_words': 587}