infiniteQuery throws "getNextPageParam is not a function" when 2+ stale pages are cached

Ouverte
#12,569 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@abu-tahir-0 y travaille déjà.

Depuis le 10/11/2026.

  • #12570 par @abu-tahir-0 — ouverte

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
42/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
typescript
Domaine
frontend

Piste de recherche

The failing path is the infiniteQuery and fetchInfiniteQuery handling in query-core when stale pages are already cached, and the error surfaces as options.getNextPageParam is not a function. Start by reproducing with the stackblitz example or a small test that seeds two pages with setQueryData, then trace where getNextPageParam is read during the refetch of existing pages. Done means the call either works without the callback or the types require it, with a regression test covering the stale multi-page case.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Describe the bug

Hey :)

I ran into this while testing query-core.

I can call queryClient.infiniteQuery without getNextPageParam as long as I don't pass pages. TypeScript is fine with it, and it works on an empty cache.

But if the same key already has 2 or more pages cached and they're stale, the exact same call throws:

TypeError: options.getNextPageParam is not a function

Same with fetchInfiniteQuery. prefetchInfiniteQuery doesn't throw, but it leaves the query in an error state.

So the same call works or crashes depending on what's already in the cache.

Thanks!

Your minimal, reproducible example

https://stackblitz.com/github/a-botermans/tanstack-query-infinite-repro

Steps to reproduce
  1. Have 2 pages in the cache for a key. The demo uses setQueryData, but loading them with useInfiniteQuery + fetchNextPage gives the same result.
  2. Let them go stale. The default staleTime: 0 is enough.
  3. Call infiniteQuery on the same key, without pages and without getNextPageParam:
queryClient.setQueryData(['pages'], {
  pages: ['page 0', 'page 1'],
  pageParams: [0, 1],
})

await queryClient.infiniteQuery({
  queryKey: ['pages'],
  queryFn: ({ pageParam }) => `page ${pageParam}`,
  initialPageParam: 0,
})

It refetches the first page fine, then throws when it needs the param for page 2.

Expected behavior

No internal TypeError for a call the types accept. Either it works without the callback, or the types should ask for it.

How often does this bug happen?

Every time

Screenshots or Videos

No response

Platform

Not platform specific. Reproduced on Node 26 and in Chromium.

Tanstack Query adapter

vanilla

TanStack Query version

v5.107.1

TypeScript version

v5.6.3

Additional context
  • The same steps work on 4.44.0 and fail on 5.0.0, so it looks like it came in with v5.
  • With the default retries in the browser, the TypeError gets retried like a network error. The call hangs for about 7 seconds before it rejects.
  • Workaround: pass getNextPageParam in the call too. Then it refetches all the pages.
Langage dominant
TypeScript
Étoiles
50.6k
Forks
4.2k
Merge moyen
8 h 37 min
PR mergées (30 j)
450

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TanStack/query

Toutes les issues de TanStack/query

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.