<commit_before>---
title: Upgrade Guide
desc: How to upgrade Quasar from older versions to the latest one.
---

::: danger Quasar v2 beta
* Until the final stable version is released, some aspects of the framework may change. We're not planning for additional changes, but unforeseen reported issues may require us to do breaking changes (unlikely, but keep this in mind). So please make sure that you read each v2 beta version's release notes carefully before upgrading.
* We plan on finalizing the Webpack 5 upgrade in Quasar CLI at some point in the beta stage.
* SSR support is temporarily disabled (will be enabled in the beta stage at some point before the stable release in Q1 2021). There is also no IE11 support (Vue 3 does NOT supports it either).
* We are still working on upgrading all of our App Extensions to Vue 3 and Quasar v2.
* Considering the above, we still recommend starting a new project with Quasar v2.
:::

::: tip Composition and Options API
You will notice that all of our documentation examples are using Vue 3's Composition API. This does NOT mean that you can't use the legacy Options API. On the contrary, maintaining Options API will actually help you on your upgrade path and make it a lot easier for you. After upgrading is done we do recommend switching to the Composition API, but by no means you are required to do so.
:::

## Older v2 to latest v2

### With UMD
Simply replace the version string in all the CSS and JS tags that refer to Quasar to the newer version.

### With Quasar CLI

```bash
# run these commands inside
# of a Quasar UI v2 project

# check for upgradable packages
$ quasar upgrade

# do the actual upgrade
$ quasar upgrade --install
```

::: warning Note for code editor terminals
If you're using a code editor terminal instead of an external one and you run `quasar upgrade` and get the error *Command not found* or *@quasar/cli* version appears to be *undefined*, you will need to go to the settings of your code editor terminal and untick the option (or its equivalent) *Add 'node_modules/.bin' from the project root to %PATH%*, then restart your code editor.
:::

### With Vue CLI

```bash
$ yarn upgrade quasar@next
```

Optionally, you may also want to make sure that you have the latest `vue-cli-plugin-quasar@next` package.

It's highly recommended to keep `@quasar/extras` package up to date too:

```bash
# optional, but recommended
$ yarn add @quasar/extras@latest
```

## Migrate to v2 from v1

**This guide refers to Quasar CLI & UMD projects**, but information from here can be used for Vue CLI too. For developers using Vue CLI on your projects already you can check out how to install the [vue-cli-plugin-quasar](/start/vue-cli-plugin) package that works with Quasar v2. You will also need to make a few changes to your main.js too (best way currently is to generate a new Vue CLI project for Vue 3 and then following the [install steps](/start/vue-cli-plugin#Add-Vue-CLI-Quasar-Plugin) for the vue-cli-plugin-quasar and check out the changes incurred to that /src folder, then apply the same principle to your current Vue CLI project).<commit_msg>feat(docs): small tweaks to upgrade guide<commit_after>---
title: Upgrade Guide
desc: How to upgrade Quasar from older versions to the latest one.
---

::: danger Quasar v2 beta
* Until the final stable version is released, some aspects of the framework may change. We're not planning for additional changes, but unforeseen reported issues may require us to do breaking changes (unlikely, but keep this in mind). So please make sure that you read each v2 beta version's release notes carefully before upgrading.
* We plan on finalizing the Webpack 5 upgrade in Quasar CLI at some point in the beta stage.
* SSR support is temporarily disabled (will be enabled in the beta stage at some point before the stable release in Q1 2021). There is also no IE11 support (Vue 3 does NOT supports it either).
* We are still working on upgrading all of our App Extensions to Vue 3 and Quasar v2.
* Considering the above, we still recommend starting a new project with Quasar v2.
:::

::: tip Composition and Options API
You will notice that all of our documentation examples are using Vue 3's Composition API. This does NOT mean that you can't use the legacy Options API. On the contrary, maintaining Options API will actually help you on your upgrade path and make it a lot easier for you. After upgrading is done we do recommend switching to the Composition API, but by no means you are required to do so.
:::

## Older v2 to latest v2

### With UMD
Simply replace the version string in all the CSS and JS tags that refer to Quasar to the newer version.

### With Quasar CLI

```bash
# run these commands inside
# of a Quasar UI v2 project

# check for upgradable packages
$ quasar upgrade

# do the actual upgrade
$ quasar upgrade --install
```

::: warning Note for code editor terminals
If you're using a code editor terminal instead of an external one and you run `quasar upgrade` and get the error *Command not found* or *@quasar/cli* version appears to be *undefined*, you will need to go to the settings of your code editor terminal and untick the option (or its equivalent) *Add 'node_modules/.bin' from the project root to %PATH%*, then restart your code editor.
:::

### With Vue CLI

```bash
$ yarn upgrade quasar@next
```

Optionally, you may also want to make sure that you have the latest `vue-cli-plugin-quasar@next` package.

It's highly recommended to keep `@quasar/extras` package up to date too:

```bash
# optional, but recommended
$ yarn add @quasar/extras@latest
```

## Migrate to v2 from v1

**This guide refers to Quasar CLI & UMD projects**, but information from here can be used for Vue CLI too. For developers already using Vue CLI on your projects you can check out how to install the [vue-cli-plugin-quasar](/start/vue-cli-plugin) package that works with Quasar v2. You will also need to make a few changes to your main.js (and also upgrade your Vue CLI project to support Vue 3) too (best way currently is to generate a new Vue CLI project for Vue 3 and then following the [install steps](/start/vue-cli-plugin#Add-Vue-CLI-Quasar-Plugin) for the vue-cli-plugin-quasar and check out the changes incurred to that /src folder, then apply the same principle to your current Vue CLI project).
{'fraction_non_alphanumeric': 0.06081187806033802, 'fraction_numerical': 0.00710788185120834, 'mean_word_length': 4.1944216570959805, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, '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': '6020460', 'n_tokens_mistral': 1773, 'n_tokens_neox': 1670, 'n_words': 1017}