Expire old page data from production-app

[Moocar]

Depends on #13004

Once a page has been requested form the server, the page data stays around in browser memory until a refresh occurs. However, page data can change. If a user keeps a web page open for half an hour, and a piece of content has changed, then ideally, Gatsby should know to request the new data.

A half-way fix for this is to store the time that a page-data.json was requested from the server. And then, when calling loader.loadPage, we check if a certain amount of time (e.g 5 minutes) has elapsed, since we last loaded it, and if so, expire the old data and re-request from the server.

See #13409 (comment) for original comment.

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contributefor more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[Moocar]

Not stale

[gatsbot]

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community!