fix: update deps

[ronag]

No description provided.

[ronag]

@dnlup I'm having trouble with npm run test and npm run coverage. Would you mind have a look? Maybe you have better luck.

undici$ npm run coverage

> undici@3.3.1 coverage
> standard | snazzy && tap test/*.js

TestExclude is not a constructor

undici$ tap test/request-timeout.js 
 FAIL  test/request-timeout.js
 ✖ Cannot read property 'paused' of undefined

function onBodyTimeout (self) {
  if (!self.paused) {
------------^
    util.destroy(self.socket, new BodyTimeoutError())
  }

  test: body timeout
  stack: |
    onBodyTimeout (lib/client.js:755:13)
    callTimer (node_modules/@sinonjs/fake-timers/src/fake-timers-src.js:423:24)
    doTickInner (node_modules/@sinonjs/fake-timers/src/fake-timers-src.js:894:29)
    doTick (node_modules/@sinonjs/fake-timers/src/fake-timers-src.js:975:20)
    Object.tick (node_modules/@sinonjs/fake-timers/src/fake-timers-src.js:982:20)
    RequestResponse.<anonymous> (test/request-timeout.js:61:15)
  at:
    line: 755
    column: 13
    file: lib/client.js
    function: onBodyTimeout
  type: TypeError
  tapCaught: uncaughtException

[mcollina]

lgtm

[dnlup]

No problem, I'll take a look at it @ronag

[dnlup]

The fake-timers update is causing the failure. Apparently, the context passed to the callbacks is undefined. Not sure if this is something we should address in undici or not yet.

[ronag]

Sounds like a bug in fake timers

[dnlup]

Sounds like a bug in fake timers

Could be, I don't understand why only the onBodyTimeout has this problem though. I would pin fake-timers to the previous version, or do we need the latest one now?

As a side note, should we enable depandabot updates?

[ronag]

Could be, I don't understand why only the onBodyTimeout has this problem though.

Yea. That's weird.

I would pin fake-timers to the previous version, or do we need the latest one now?

We can pin. I'll do so.

As a side note, should we enable depandabot updates?

I'm neutral. @mcollina wdyt?