Daniel Roe
Daniel Roe
Would you provide a reproduction please? 🙏
This is the intended behaviour. You can control what message is returned on a server endpoint by calling `throw createError({ })`: https://v3.nuxtjs.org/api/utils/create-error#throwing-errors-in-api-routes. Can you explain more about what you feel...
We have some potential improvements we can make regarding unhandled/handled errors - might be worth wrapping this discussion into that. cc: @pi0.
Would you provide a reproduction? 🙏
FYI (and this may be the issue also with @jaythegeek if you are just setting `head`) the config key to use is `app.head`: ```js export default defineNuxtConfig({ app: { head:...
This should be resolved in the [edge channel](https://v3.nuxtjs.org/guide/going-further/edge-channel/), or in the next RC. Let me know if not.
@Gyurmatag Have you tried changing the import as the error message suggests? Would you provide a minimal reproduction? 🙏
Please check whether [the edge channel](https://v3.nuxtjs.org/guide/going-further/edge-channel/) resolves things for you, and if not, please do provide a minimal reproduction. 🙏
You can provide a minimal repository that doesn't work when deployed.
cc: @pi0