And it more, that im wondering why and how it happens - as I am in the process of refactoring the whole fetch, to use the BFF-strategy. which should fix it (I hope 🤓 )

@danielroe.dev this is the best i can do, hope this helps clearify things a bit:
github.com/djrasmusp/pr...

I trying to create a repo with minimal of the setup :)

And many thanks for helping and answering so quick

it a useAsyncData with $fetch, see the error. But we also proxy "/media" to the img url, in the CMS. and this also "loses" connection

So in some way, it feels like that after +5 min, something in the proxy/h3/routesRules shuts off, and the client side calls the CMS directly
.

I know its difficult, was hoping for some pointer in which direction to look.

Dont know if a quick repo of how we set it up on the nuxt side would help ?

The reason for this, is that is only the nuxt server side that can communicate with the CMS, because of Firewall rules. So we cant make client-side calls.

Everything works on the "first" render, but if left idle then is just stops working

Thanks for the info

Congrats to you, @atinux.com @pi0.io and @antfu.me :) looking forward to the future

Couldnt you use the to send it to the “front” ? developer.mozilla.org/en-US/docs/W...

Oh sad to hear its like that :( I going to the conf this year, so thought there was something I missed as a visitor

what news should there ? what have i missed

Thank you both for the answer ;) just what I need :)

Sorry, misunderstood you - but then i got the training for making the next issue report.

Thanks

Great, I have made the issue and PR now :)

I would say yes. Just a simple version with the options to add image, title, description and cta.
Just as help to show how to start the component.

Looking foward to reading it 🤓