-
-
Notifications
You must be signed in to change notification settings - Fork 29
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[vue-composition-api] must call Vue.use(VueCompositionAPI) before using any function. #18
Comments
This error still exist after nuxt/framework#3906. Am i doing something wrong @danielroe? Sorry for a lot of interruptions 🙏 |
It looks like I need a reproduction 🙏 |
i cannot reproduce but i found where the problem is came from. i closed the and there's no error here. i think @posva can help us for this? @danielroe |
https://github.com/devind-team/eleden cd client |
Completely impossible to work because of this error :( |
yes same for me. i installed old version. @danielroe any update for this error? |
I created a simple project with nuxt-bridge & nuxt/pinia. https://github.com/Luferov/bea. Maybe the problem is not in nuxt-bridge, but in pinia/nuxt? @danielroe is it possible? |
i think it's possible. but this error occurs after nuxt/framework#3900. and nuxt/framework#3900 resolves #94. btw |
Ok, with nuxt3 it`s wokr fine. |
This will likely be resolved with vuejs/pinia#791. For now I think you can work around this with: import { defineNuxtConfig } from '@nuxt/bridge'
export default defineNuxtConfig({
modules: ['@pinia/nuxt'],
build: {
transpile: ['pinia'],
},
}) Let me know if that doesn't work. |
that's not worked. :( But somethings it weird now. I tried on workarounding at any page. I didn't get this error if i remove all nuxt things(like useLazyAsyncData, auto imported composables and pinia stores). If i use any one of these i got error again. |
Unfortunately, the same effect :( I do commit to reproduction https://github.com/Luferov/bea. |
And got this warning brefore this error, @danielroe should I create a new issue or not about this or not? |
@Luferov Yes, it's a different issue. However I think that you just need to ensure you're on the latest version of |
I wonder if you have solved this problem, because I seem to have the same problem |
@antlionguard Could you try to do like that? |
Is this a plugin? If so, did you import it in "plugins" inside the nuxt.confg? I'm asking to confirm if I understood correctly. |
When I fixed all other issues, unfortunately this error reappeared. :( very sad |
|
I think the whole team is focused on nuxt3. May need to wait a bit. |
I work around with transpile after new updates. And pinia now working. @Luferov with this: import { defineNuxtConfig } from '@nuxt/bridge'
export default defineNuxtConfig({
buildModules: ['@pinia/nuxt'],
build: {
transpile: ['pinia'],
},
}) But there's another nuxt instance unavaliable error appears. I will create another issue for new error. |
Forward to another problems.)) |
The new problem related with directly nuxt-bridge. I got the error on nuxt context used pages like "ref, computed, useNuxtApp". |
Sorry for wrongly opened issue. I cannot edit labels. This issue related with
bridge
🙏There's something broke after this PR. I got this error in my all pages.
_Originally posted by @antlionguard in #94
The text was updated successfully, but these errors were encountered: