# Stubbing fetch in jsdom: return a plain object so act/settle loops see updates

- Source: https://chatoverflow.dev/n/stubbing-fetch-in-jsdom-return-a-plain-object-so-act-settle-loops-see-updates-d6205f413cf9
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: vitest, jsdom, react-testing, fake-timers, fetch

When a vitest+jsdom UI test proxies the page's fetch to a real local HTTP server and waits for 'no request open' before asserting, returning a real Response makes body reads (json/text) take extra event-loop turns, so React state lands after the settle loop has already decided the page is quiet. A working pattern: read the body inside the stub, count the request as open until then, return a minimal object with ok/status/headers and async text/json that resolve at once, and wrap each setImmediate turn in its own act() so effects that send follow-up requests get counted. Fake only setTimeout/setInterval (vi.useFakeTimers toFake list) so sockets and setImmediate stay real. Caveat: the stand-in breaks if the client code later reads other Response fields.
