Vue 2 → Vue 3

One-screen report · Looks like your app Read the changelog →

Vue 2 → Vue 3

Days

Med risk

Vue 2 reached end-of-life on 2023-12-31. This guide covers the upgrade and the Mushi Mushi pieces.

The Mushi Mushi Vue adapter (mushi-mushi/vue) supports Vue 3.3 and later (its peer dependency is vue >=3.3). Apps still on Vue 2 use the plain mushi-mushi web SDK; this guide brings you onto the adapter.

Vue 2 is no longer receiving security patches. The Vue team’s official recommendation is to migrate. If you cannot, HeroDevs ships a paid LTS for Vue 2.7 with security backports.

What changes (high level)

new Vue({...}).$mount(...) → createApp(App).mount(...)

Options API still works in Vue 3, but the Composition API is the recommended style. You can mix both during the migration.

Filters are gone. Methods or computed properties replace them.

Functional components are plain functions in Vue 3; the functional option and <template functional> are gone.

v-model on a custom component changed semantics; see the Vue 3 migration guide .

Vue Router 3 → 4. Vuex 3 → 4 (or Pinia, recommended).

Mushi Mushi: mushi-mushi direct usage → mushi-mushi/vue adapter.

API mapping (Mushi Mushi)

Vue 2 (with `mushi-mushi`)	Vue 3 (with `mushi-mushi/vue`)
`Mushi.init({ projectId, apiKey })` in main.js	`app.use(MushiPlugin, { projectId, apiKey })` only; the plugin calls `Mushi.init()` itself
Manually attach `Vue.config.errorHandler = ...` to forward to Mushi Mushi	The adapter chains onto Vue 3’s `app.config.errorHandler` automatically
Use the instance from `Mushi.init()` in components	Use the `useMushi()` composable inside `<script setup>` / `setup()`

Vue 2 (with mushi-mushi)

Vue 3 (with mushi-mushi/vue)

Mushi.init({ projectId, apiKey }) in main.js

app.use(MushiPlugin, { projectId, apiKey }) only; the plugin calls Mushi.init() itself

Manually attach Vue.config.errorHandler = ... to forward to Mushi Mushi

The adapter chains onto Vue 3’s app.config.errorHandler automatically

Use the instance from Mushi.init() in components

Use the useMushi() composable inside <script setup> / setup()

Migration checklist

Common gotchas

Calling Mushi.init() as well as app.use(MushiPlugin, ...). Since @mushi-mushi/vue 1.0 the plugin initialises the SDK itself; a second Mushi.init() only logs “Already initialized”. Remove it.

<script setup> and Options API mixing. Both work in Vue 3, but useMushi() is a composable, so call it inside setup() / <script setup>. In an Options API component, add a setup() option that returns it, or use Mushi.getInstance() from mushi-mushi.

Stale Vue 2 plugins. Check each Vue plugin you use (error reporting, logging, UI kits) for a Vue 3 version.

What changes (high level)

API mapping (Mushi Mushi)

Migration checklist

Common gotchas

Mushi Mushi during the migration

References