InitialData breaks SSR

[thebuilder]

Trying to render an application with some initialData, which triggers some async calls.

if (query.state.data) {
   query.scheduleStaleTimeout(); // Simulate a query healing process

    query.heal(); // Schedule for garbage collection in case
    // nothing subscribes to this query

    query.scheduleGarbageCollection();
}

The scheduleStaleTimeout() and scheduleGarbageCollection() can be prevented from running by setting stale and cache to Infinity, but heal() will always call a clearTimeout function.

In our server environment calling setTimeout or clearTimeout throws an error.

The fix is to add the isServer check to the if statement - I'm just not sure if there's any consequences to doing this? Does the server actually need to call any of these methods?

[thebuilder]

If others are wondering, the current "fix" for this in my application is the skip initialData when rendering serverside, and just use it.

function App(props) {
  const { data: pageData } = usePageData(useQuery, loadPageData, {
    initialData: !process.env.SERVER ? initialData : undefined,
  });
  let data = pageData || initialData;
}

[thebuilder]

Thanks for the quick fix!🙏

[tannerlinsley]

My pleasure

…

On Apr 20, 2020, 10:17 AM -0600, Daniel Schmidt ***@***.***>, wrote: Thanks for the quick fix!🙏 — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

[cherniavskii]

@thebuilder Just out of curiosity, what is your server environment?