8ear
Not SSG
This issue has been resolved.
It was caused by something written in $fetch.
The part where the API was retrieved with useFetch was SSG, and it seemed that the part written in $fetch was calling the API even though SSG was set.
I hope this can be of some help to anyone who is experiencing the same thing.
35 replies
Not SSG
@manniL / TheAlexLichter
That's right.😓
Thank you for listening to me so kindly.
I would really like to show you everything, but it's a work project so I can't.
I'll come back to you and ask for your help when I figure out how to reproduce it.
Thank you for your time!
I've subscribed to your YouTube channel!
35 replies
Not SSG
@manniL / TheAlexLichter
Thank you for your kind reply.
I still haven't figured out how to reproduce the problem, but a project created in a similar way (using the same base nuxt.config.js settings and calling the API in the same way) works as expected.
By the way, here is the sample I created.
But I can't reproduce the problem with this one.
https://github.com/P0lar8ear/kuroco-nuxt
35 replies
Not SSG
@manniL / TheAlexLichter
All pages are being generated.
However, the API is being called on the client side and this problem is not being solved, so I suspect there may be a problem with the way the API is being called.
When I looked into it, I found literature that said that useFetch doesn't work and that asyncData should be used, so I'm confused. Even when I rewrite the parts that use $fetch to asyncData, the root cause is not solved... (although I feel like the way asyncData is being used is not relevant to this case in the first place)
I don't know how to debug because generate completes without any errors.😭
35 replies