Daniel Roe
Daniel Roe
Do you still experience this?
This is an issue for Nuxt 3. i'm closing this but if you can provide a reproduction I'll happily reopen.
Likely your npm cache is outdated: https://unpkg.com/browse/mlly%400.5.10/. Try reinstalling or running `yarn upgrade` to pull in the latest version of nitropack with fix: https://github.com/unjs/nitro/commit/6cad6821039328e099b4b1a6cba5f73eba42a111.
@gkatsanos This is working as intended. See https://codesandbox.io/s/awesome-chaplygin-4n9wl?file=/pages/index.vue for an example. You shouldn't expect to see logs in your devtools for actions carried out on server, although that might be...
@gkatsanos Seems to be working for me. ![CleanShot 2021-03-11 at [email protected]](https://maintainers.s3.fr-par.scw.cloud/Clean_Shot_2021_03_11_at_16_42_46_2x_430c0a1a6c.png)
Basically after an async operation, we no longer have access to the nuxt context (to avoid sharing state with other requests). Vue composables should almost _always_ be synchronous, with a...
Let's track in https://github.com/nuxt/framework/issues/6996.
@Soviut PRs definitely welcome to improve the docs :grinning: However, I'm not sure that's correct - you can return other errors using `error` ([see docs](https://nuxtjs.org/docs/2.x/internals-glossary/context#error)) which trigger this page being...
@OyewoleOyedeji Is this something you're experiencing with the nuxt/nuxtjs.org repository, or is this a more general issue you're facing?
Linking this here just in case it's useful: https://github.com/histoire-dev/histoire/blob/main/packages/histoire-plugin-nuxt/src/index.ts#L56