jd
jd
NNuxt
Created by jd on 9/20/2024 in #❓・help
Fix for <stdin>:34:12: ERROR: Expected identifier but found ":"
@julbd it just stopped on its own the next day. I don't think I even made a change for it The transform I thought might have been connected to the transform parameter function inside the useFetch I have, if you do that yourself
3 replies
NNuxt
Created by jd on 8/22/2024 in #❓・help
Best way to save user context to avoid needing to fetch at every page?
Thanks for taking the time to answer! I'm running into the same nasty issue than here, after all: https://github.com/nuxt/nuxt/discussions/25602 I'm calling the composable from the nuxt/middleware (not server/middleware) and I'm getting that error
3 replies
NNuxt
Created by jd on 8/20/2024 in #❓・help
Docker and Nuxt in production
The config is api:8000 and it treats api as a string instead of the network address
7 replies
NNuxt
Created by jd on 8/20/2024 in #❓・help
Docker and Nuxt in production
I realized that SSG isn't the way to go, but wouldn't a build (SSR) work for that purpose? I've actually been able to make it work, but I'm running into a new challenge now, the api container/host doesn't resolve
7 replies
NNuxt
Created by jd on 7/11/2024 in #❓・help
Best practices for state/composable to depend on fetched data?
I still have the problem that running useAsyncData in a composable returns a 500 And I can't, for the life of me, understand how to use runWithContext
6 replies
NNuxt
Created by jd on 7/11/2024 in #❓・help
Best practices for state/composable to depend on fetched data?
Seems linked to the use of useAsyncData in the composable (from the stack)
6 replies
NNuxt
Created by jd on 7/11/2024 in #❓・help
Best practices for state/composable to depend on fetched data?
Hey @Mähh thanks a lot! I love the simplicity of the suggestion! I still have the same error I had before.
[500] [nuxt] A composable that requires access to the Nuxt instance was called outside of a plugin, Nuxt hook, Nuxt middleware, or Vue setup function. This is probably not a Nuxt bug.
[500] [nuxt] A composable that requires access to the Nuxt instance was called outside of a plugin, Nuxt hook, Nuxt middleware, or Vue setup function. This is probably not a Nuxt bug.
6 replies