DX: Next.JS complain about using `Date.now()` inside a Client Component

[H01001000]

TanStack Table version

v8.21.3

Framework/Library version

React 19.2.0 Next 16.0.3

Describe the bug and the steps to reproduce it

It's a pure DX issue, where Next.JS will show an issue when Date.now() is used in a client component, mainly to tell devs not to use it, where it leds to the render on server and client might differ.

TanStack Table used Date.now() in memo function, note there is no way to switch it off, opts.debug is always defined shows here.

I suggest either making getMemoOptions return undefined, or changing to use performance.now(), which Next.JS will not complain, note need to take care edge case like #3830, tho engine version is set to >= 12.

Extra Next.JS docs: here

If a maintainer decided, I can help open a PR for that

Your Minimal, Reproducible Example - (Sandbox Highly Recommended)

N/A

Screenshots or Videos (Optional)

No response

Do you intend to try to help solve this bug with your own PR?

Yes, I think I know how to fix it and will discuss it in the comments of this issue

Terms & Code of Conduct

• I agree to follow this project's Code of Conduct
• I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.