I'm running into a problem with `initialPageParam` here. My api expects no or an empty initial page parameter. `initialPageParam=""` generates code that sends `page=0`. I believe the reason is that `formatOptions => safeParseNumber` converts the empty string to `0`.

[7nohe]

          I'm running into a problem with `initialPageParam` here. My api expects no or an empty initial page parameter. `initialPageParam=""` generates code that sends `page=0`. I believe the reason is that `formatOptions => safeParseNumber` converts the empty string to `0`.

I can work around it by setting initialPageParam="''" which generates code that sends page=%27%27 which works with my api but it's a bit ugly.

Ideally there would be a omitInitialPageParam parameter that would change it so that no page parameter is send at all.

Originally posted by @JonasPf in #149 (comment)

[7nohe]

Both halves of this are now fixed on the v3 branch and will ship in 3.0.0.

1. Blank initialPageParam no longer becomes 0 (fab6733). safeParseNumber relied on Number(value), and Number("") is 0, so formatOptions coerced --initialPageParam "" into a numeric 0 — exactly the diagnosis @JonasPf gave. Blank and whitespace-only strings are now treated as NaN, so the value is preserved. The initialPageParam="''" workaround is no longer needed.

2. New --omitInitialPageParam flag (f6014eb) for the "send no page param at all" request. It emits initialPageParam: undefined and spreads the page param into the request only once TanStack Query supplies one, so the first request carries no page param. It overrides --initialPageParam.

Both were verified end-to-end: the generated output typechecks against the example app across all four infinite surfaces (hook, suspense, prefetch, and the infiniteQueryOptions factory). Thanks @JonasPf for pinpointing the root cause.