Closed sig9 closed 2 years ago
Maybe @danielroe could guide you about the best place to debug.
This looks like either an issue with Nitro or Content. Let's raise with content first - would you be able to open an issue there with a reproduction, and tag me to look into it?
Closing here in the meantime
Studying Content and Nitro a bit before I open the ticket.
I have noticed a rendering issue when a route is visited for the first time after a build with NITRO_PRESET=azure
Steps to reproduce:
This should start the azure static web app cli on localhost:4280 which proxies requests to static pages and functions.
When I navigate to localhost:4280 the / route renders nicely. Clicking About in the nav bar yields the results in the image below. Reloading http://localhost:4280/about shows the properly rendered /about route.
Alternately, if I first navigate to localhost:4280/about it will render nicely. Then clicking on the Home link in the nav bar shows raw json from the path="/" content query.
Seems to need a full reload on each route. I suspect there is some state preserved serverside because after all the routes have been hit once, I can open the pages in a different browser or incognito and the issue is no longer there.
I see this issue when running builds locally and also when builds are freshly deployed to azure static web apps.
I'm guessing this might not be the right place to report this. I would appreciate any debug tips or redirects.