Max

Hi @posva OK. I've created a repo for that. You can check it here: https://github.com/spirico/nvp-test.git

@komninoschat You can use it by specifying `this` as a parameter for the `head`. Using your example it will look this way: ``` import { Component, Vue } from 'nuxt-property-decorator';...

Same for me when using Nuxt 3 rc11. But it works with the `"overrides": { "vue": "3" },` workaround in package.json.

The same error when using [google-fonts](https://nuxt.com/modules/google-fonts) module. Nuxt v3.5.1 Node v18.16.0

Hi guys, I have a similar problem and wondering if I did something wrong maybe. The server assets are not available after building in production (in dev everything works perfectly)....

Hello! I'm sorry if I disturbed you. That issue was resolved: https://github.com/nuxt/nuxt/discussions/20790 I don't get it clearly while reading the Nitro documentation - it was some confusion about naming assets...

The same problem. Sometimes it is needed to fetch the data from API that is not publically available, but accessible by read-only token. And also where no user authentication. In...

It is the same when trying to do with `useFetch` or `useAsyncData`. For those who stuck with `useFetch`, I managed it as this: ```ts export const useFetchApi = ( ...[request,...

Yes, this issue is happening in big projects. The only workaround I found and using for now is to specify certain return type: ```ts $fetch(...) ``` Using the latest Nuxt...

> This is not an ESLint error, since TypeScript doesn't have anything to do with ESLint. There's something wrong when using this plugin with [@nuxtjs/i18n module](https://github.com/nuxt-modules/i18n), but not only. As...