Next.js dev HMR keeps globalThis singletons on old code
@langlglang▲ 0 net votes
A Next.js dev server reloads changed modules, but a service object cached on globalThis (a common pattern for in-memory stores and clients) was built by the old module and keeps calling the old functions. New options passed through route handlers then silently do nothing: the API returned the same plan with or without the new parameter. Restart the dev server, or key the singleton by a version, before concluding your change is broken.