Runtime warning - Invalid prop: type check failed for prop 'container'

[hamblin]

Versions

• 1.7.10

Describe the bug

Just installed 1.7.10 (previously running 1.7.8) and I now get a Vue runtime warning about invalid prop for 'container' in plugin options, even using default value for container (document.body).
Exact wording of the warning:
[Vue warn]: Invalid prop: type check failed for prop "container". Expected Object, Function, got HTMLBodyElement

I have it Installed as a plugin (standard Vue CLI, not Nuxt), running Vue 2.6.12.

Toasts still show, but warning is still unexpected.

Expected behavior

Should be able to use like this without prop type check failure.

Steps to reproduce

Reproduction
Steps:

1. Install 1.7.10 as a plugin (ie: Vue.use(Toast, options))
2. Use default value for 'container' in options (document.body)
3. Observe runtime warning for failed prop type check.

Here is my code for installing it as Vue plugin. I get the same result if I don't specify container in options object (use default) or if I explicitly specify container: document.body.
import Toast from "vue-toastification"; const toastificationOptions = { position: 'top-right', timeout: 3000, toastClassName: 'spl-toastification', transition: 'Vue-Toastification__fade', }; Vue.use(Toast, toastificationOptions);

Your Environment

• Device: MacBook Pro - MacOS 10.15.6
• Browser: Chrome 87
• Vue 2.6.12 (full build)

Additional context

I see you made a change to prop validation for plugin options in 1.7.10... so I'm guessing that's where the issue is.

[dmanva]

I have the same warning. Vue 2.6.12

[pieinn]

Same warning Nuxt @ v2.14.12

[Maronato]

Hey all!
Thanks for reporting this. It seems that runtime prop validation for the container prop is not possible without breaking SSR support, therefore I've disabled it.

The fix has been released in v1.7.11. Please give it a try and reopen the issue if the problem persists :)