Replies: 4 comments 2 replies
-
This makes installing plugins more aligned with other Nuxt API's and abstracts vue 2 / vue 3 transition. I like it. |
Beta Was this translation helpful? Give feedback.
-
Prefer the config way for making it clear that nuxt plugins inject into nuxtApp while vue plugins inject into vue. But I am not sure whether enforcing nuxt.config in module is correct. Besides, it is weird too that nuxt modules inject into vue. Btw, maybe there need to be options for server/client in config. |
Beta Was this translation helpful? Give feedback.
-
Anything that makes the migration from Nuxt 2 (bridge) to Nuxt 3 easier is going to increase retention. Great proposal - I will definitely use 💯 |
Beta Was this translation helpful? Give feedback.
-
After thinking of it, since we have the auto-import of plugins, this is more than enough and this might be the extra abstraction layer that we don't want. |
Beta Was this translation helpful? Give feedback.
-
It is common that both users and modules to install a vue plugin. Supporting shortcuts allows a managed way to use vue plugins and also makes it easier for bridge support for module authors (vue2 uses global plugins using
Vue.use
vs vue3 usingapp.use
)Modules API:
Nuxt Config API:
Runtime API (nuxtApp within nuxt plugins):
Beta Was this translation helpful? Give feedback.
All reactions