Fix cannot assign to read only property 'exports' (issue #335)

[MelvinSnijders]

Description

Removed export keyword from the useToast() method.

Related Issue

335

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [x] All new and existing tests passed.

[dancing-bear-blues]

I have been up and running for the last few days with this fix in place and do not have any side effects to report. I would like to see this change merged.

[lukaszarpak]

I found a solution.

Create your own composable and then use it the same way as described in the docs. Just make sure that vue-toastification/nuxt is added to modules in nuxt.config.js so it's injected into useContext().app.

---

Add these:

./nuxt.config.js

modules: [
    'vue-toastification/nuxt',
]

./composables/useToast

import { useContext } from '@nuxtjs/composition-api'

export const useToast = () => useContext().app.$toast

---

Usage:

import { useToast } from '@/composables/useToast'

// in setup()
const toast = useToast()

// use toast the same way as described in the docs