How should we acces to nuxt context on Nuxt3

[david8z]

When accesing nuxt context for example this.$nuxt.route.params on Nuxt3 I get the follwing warnings

Accessing __v_isRef is not supported in Nuxt3.

Accessing __v_isReadonly is not supported in Nuxt3.

Is there a different recommended way?

[Lanayx]

I'm getting the same warnings when using composables for example
const event = useRequestEvent(this.$nuxt)
however it still works even with warnings

[bros4president]

Same here! Is this a Nuxt issue or Pinia?

[huangbh1024]

i also have this promble ,how to resolve it

[HendrikJan]

To get route information in Nuxt3 you can use:

const route = useRoute();
const router = useRouter();

[marianheinsen]

Same problem for me

[nikkistorme]

I'm having the same issue. I want to use Nuxt context from inside a Pinia store so I can access the useSupabaseClient composable, but I'm getting the same errors @david8z mentioned above.

My action:

    async signIn(credentials) {
      this.loading = true;
      const supabase = this.$nuxt.useSupabaseClient();
      await supabase.auth.signIn({
        email: credentials.value.email,
        password: credentials.value.password,
      });
      this.loading = false;
    }

Console message:

Accessing __v_isRef is not supported in Nuxt3.
Accessing __v_isReadonly is not supported in Nuxt3.
Accessing useSupabaseClient is not supported in Nuxt3.

[LinusBorg]

This error is coming from nuxt, not pinia. Here's an example of an older issue where some other 3rd party lib triggered this in Nuxt3, and it was fixed in Nuxt. So I'd assume it's also something to fix on their end.

[T-Zahil]

Any news about this? We still can't access the context from Pinia despite what's explained in the docs 😕

[bros4president]

@T-Zahil and everyone else reaching this thread:

From @pinia/nuxt 0.3.0 onwards, you can access nuxt with useNuxtApp(), globally in a store.

So you just need to replace this.$nuxt.foo with useNuxtApp().foo (or assign useNuxtApp output to a variable of course).

This is due to Nuxt dropping legacy context in rc.5.

Thanks to the team for taking care of this caveat. Logs are way cleaner now without the warnings :)!