fix(#2591): findComponent
doesn't not return exposed properties in vm
#2715
+9
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After investigating the issue down to
@vue/runtime-core
it appears thatexposeProxy
is only set in a script-setup component if it uses at least one directive:https://github.com/vuejs/core/blob/main/packages/runtime-core/src/component.ts#L1187
https://github.com/vuejs/core/blob/main/packages/runtime-core/src/directives.ts#L143
Meaning a component can have an exposed API while
exposeProxy
isnull
. In this case we can create manually fromexposed
which essentially has the same effect, because the one created by runtime-core is only different by also proxyingpublicPropertiesMap
which aren't available anyway.