Can't get componentInstance property of vnode when using the v-slot directive on a <template>.

[xiejay97]

Version

2.6.11

Reproduction link

https://github.com/Xie-Jay/slot-issue

Steps to reproduce

I show issue by console.

What is expected?

All vnode can get componentInstance property.

What is actually happening?

ComponentInstance property is undefined when using the v-slot directive, but others not.

<slot-test>
  <component-test slot="default" name="slot1"></component-test>
</slot-test>
<slot-test>
  <template slot="default">
    <component-test name="slot2"></component-test>
  </template>
</slot-test>
<slot-test>
  <template v-slot:default>
    <component-test name="slot3"></component-test>
  </template>
</slot-test>

---

When I use v-slot to replace slot, I get this diffrence which really confuse me.

[posva]

I'm not sure you are supposed to use componentInstance from the returned vnode. You can still get the component instance through $children[0]

[xiejay97]

I'm not sure you are supposed to use componentInstance from the returned vnode. You can still get the component instance through $children[0]

It's useful for me to build component that need control components in slot by using componentInstance.

I tried to use $children, it's ok when just one slot.

But more than one, like this:

<div>
  <slot />
  <slot name="expand" />
</div>

It will be difficult to separate these components in slot by using $children.

In fact, I have no idea except that provide extra prop to distinguish them, because there’s no order guarantee for $children.

[hanotao]

@rubys @rubys @rubys @rubys 666