Harry Talbot

This would be really useful for us - maybe a `toHaveBeenCalledNTimesWith` would be more flexible?

Yep, I completely agree, I'll get a reproduction sorted. I don't expect help from maintainers until then, fwiw

FWIW, we found that `register.clear()` looked like it fixed things locally. But in our production build (Next.js) `clear()` was clearing all metrics collected by `collectDefaultMetrics` too. I assume not visible...

Hi @lforst any update on this?

Hi @lforst just wondering if you could give any estimates as to if/when this would hit roadmap for a Sentry release. We currently have 8.4k events all grouped in Sentry...

Hi @milesrichardson, In the repro above this is also an issue on Node 16 and 14. Have updated the issue description. There is some discussion in https://github.com/mswjs/msw/issues/1388 around using `cross-fetch`...

Currently upgrading to v2, with Node 20.9, and now on Jest 29. The following config seems to work: ```tsx const mockDate = new Date(2022, 6, 26); beforeEach(() => { jest.useFakeTimers({...

Cheers @kettanaito - have to say upgrading our codebase from v1 -> v2 (~150 rest resolvers) was an absolute breeze, largely thanks to the fantastic new docs 🎉

Any update on this issue? Really interested in this as I think I've run into a similar problem. Not sure of the best way around this, with strict mode due...

For simple default metrics, creating an api route works well in Next.js: ```tsx collectDefaultMetrics({}); const prometheus = async (_req: NextApiRequest, res: NextApiResponse) => { res.setHeader('Content-type', register.contentType); res.send(await register.metrics()); }; export...