- Notifications
You must be signed in to change notification settings - Fork278
fix(#2591):findComponent doesn't not return exposed properties in vm#2715
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
netlifybot commentedSep 30, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
✅ Deploy Preview forvue-test-utils-docs ready!
To edit notification comments on pull requests, go to yourNetlify project configuration. |
cexbrayat left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thank you for looking into it. Would you mind adding a unit test that showcases that the issue no longer exists?
cexbrayat commentedNov 7, 2025
Would you mind adding some unit tests to the PR so we can merge it? |
adamberecz commentedNov 7, 2025
I've stumbled upon another issue related to using |
After investigating the issue down to
@vue/runtime-coreit appears thatexposeProxyis 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
exposeProxyisnull. In this case we can create manually fromexposedwhich essentially has the same effect, because the one created by runtime-core is only different by also proxyingpublicPropertiesMapwhich aren't available anyway.