Route "/" used Date.now() instead of using performance ... when using TanStack react query and dynamicIO

[spaceo]

Link to the code that reproduces this issue

https://github.com/TanStack/query

To Reproduce

1. Create a query client provider
2. In layout wrap the children in the provider
3. Start the app in dev mode
4. When loading the app the error will occur

Related to this issue:
#72024

Current vs. Expected behavior

I would expect no error to happen :)
But apparently the QueryClient uses a "forbidden" way to handle current time in its cache evaluation.

Provide environment information

/bin/sh: pnpm: command not found

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:11 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.1.1-canary.0 // Latest available version is detected (15.1.1-canary.0).
  eslint-config-next: 15.0.3
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.6.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Runtime

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

[thatguyinabeanie]

I am also experiencing this bug as well

[TechFeatured]

I was able to remove this error by wrapping my Provider in a server component and calling await connection - then wrapping the call in Suspense.

async function QueryProviderOuter({ children }: { children: ReactNode }) {
  await connection();
  return <QueryProvider>{children}</QueryProvider>;
}

<Suspense fallback={<LoadingSpinner />}>
                        <QueryProviderOuter>
                          <main className="flex-1">{children}</main>
                        </QueryProviderOuter>
                      </Suspense>

unsure if this opts the entire subtree into client rendering though

[gnoff]

@TechFeatured yeah this will essentially opt everything downstream of this layout into being dynamic only. With PPR you can maybe still have a very generic static shell but since this is presumaly quite high in the application hierarchy no deeper layouts with their own Suspense boundaries will end up being prerendered. I can see that this use of Date.now() is related to coped mutations. I don't know yet whether there is an upstream change in react-query that could make this feature compatible with prerendering with dynamicIO. I'll dig in a bit and see if I can make sense of it

[gnoff]

I've opened a PR in Tanstack-query that will address this issue if landed. Will revisit once there is movement there

[Esequiel378]

Hey! I saw your PR merged a couple of hours ago (excellent work by the way, @gnoff ). Do you have a rough idea of when this would be available? Or if there is a way to use this new change in the meantime 🤗

[eps1lon]

Fixed in TanStack/query#8496 which was release in https://github.com/TanStack/query/releases/tag/v5.62.12

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.