feat(runtime-core): export currentInstance methods#5472
Conversation
|
❌ Deploy Preview for vuejs-coverage failed. 🔨 Explore the source changes: 414cf91 🔍 Inspect the deploy log: https://app.netlify.com/sites/vuejs-coverage/deploys/62220dcdfe83880007903cd6 |
|
✔️ Deploy Preview for vue-next-template-explorer ready! 🔨 Explore the source changes: 414cf91 🔍 Inspect the deploy log: https://app.netlify.com/sites/vue-next-template-explorer/deploys/62220dcd35403800073a86e4 😎 Browse the preview: https://deploy-preview-5472--vue-next-template-explorer.netlify.app |
❌ Deploy Preview for vue-sfc-playground failed.
|
|
I'm not sure we feel comfortable exposing hooks into these internals. Can you share a bit more about the use case and what problem this solves? |
|
@LinusBorg I actually wrote a lot about that here That said, how about we export this under a namespace similar to how we export SSR utils? |
|
a workaround see #4611 (comment) |
Size ReportBundles
Usages
|
@vue/compiler-dom
@vue/compiler-sfc
@vue/compiler-ssr
@vue/reactivity
@vue/runtime-core
@vue/runtime-dom
@vue/server-renderer
@vue/shared
vue
@vue/compat
@vue/compiler-core
commit: |
|
Would be nice to have these methods expose for other libraries to use... |
Close #4611
Hi, I'm maintainer of reactivue. I rewrote it from scratch and managed to shrink it down to ~150 lines by using EffectScope API. But to support Vue plugins like
pinia,@vueuse/headI needed to accesssetCurrentInstancemethod.