-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(query-core): use performance instead of Date.now to initialize mutationId #8315
base: main
Are you sure you want to change the base?
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit efbf935. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution
✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
"react": "19.0.0-rc-7ac8e612-20241113", | ||
"react-dom": "19.0.0-rc-7ac8e612-20241113", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we please use 19.0.0-rc.1
, and use it everywhere. I’d really like to have the versions streamlined, thanks 🙏
0ef3c9e
to
efbf935
Compare
Previously the
MutationCache.#mutationId
was initialized withDate.now()
. When usingdynamicIo
with Next it was throwing:The error is fixed by using
performance.timeOrigin + performance.now()
instead.I have updated the
next
andreact
dependencies on the Next 15 integration and example from RC to stable. However, thedynamicIo
is still an experimental feature and requires the canary dependency, so this not tested. I can confirm that the error was thrown locally byreact-next-15
integration when enablingdynamicIo
, and this change fixes it.Closes #8277