Can I force a +data hook to re-run after serving page from static file?

[sebastian-eggers-pcg]

My situation:

• I have a page-component.
• The page loads data from an external api in a +data.shared.ts hook.

What I an trying to acomplish:

• I want to pre-render the app, and serve it as static files. This works.
• I want the page-component to load the data from the external api on client-navigate. This works.
• I want the initial user request (being served from the corresponding static file) to first display the data that was baked into the build (works), but then request the data from the external api, to make sure that the user sees current data.

I have not yet found a good way to implement the last step.

For example, to make more clear how I imagine the behaviour:

• At the build-time, the external api returned {someValue: 1}.
• Today the external api returns {someValue: 2}.
• The user loads the app, and is served by the pre-rendered file.
• The user sees value 1, but then the external api is called and the user sees value 2.

I have found a workaround by triggering a navigation inside the component:

if(!context.isClientSideNavigation){
  navigate(context.urlOriginal);
}

But this does not seem to be a good solution. Is there a better way?

[brillout]

Have you seen #1476 ?

I have found a workaround by triggering a navigation inside the component:

What makes you think this is a workaround? Isn't exactly what you want actually? FYI you can use reload() in case the URL doesn't change.