Nock v13.0.0-beta.2 Release Notes
Release Date: 2020-04-04 // about 4 years ago-
13.0.0-beta.2 (2020-04-04)
🐛 Bug Fixes
💥 BREAKING CHANGES
Calling
request.abort()
:- Use to always emit a 'socket hang up' error. Now only emits the error if
abort
is called between the 'socket' and 'response' events. - The emitted 'abort' event now happens on
nextTick
. - The socket is now only destroyed if the 'socket' event has fired, and now emits a 'close' event on
nextTick
that propagates though the request object. request.aborted
attribute is set totrue
instead of a timestamp. Changed in Node v11.0 nodejs/node#20230- Calling
write
,end
, orflushHeaders
on an aborted request no longer emits an error.
However, writing to a request that is already finished (ended) will emit a 'write after end' error.
🤡 Playback of a mocked responses will now never happen until the 'socket' event is emitted.
The 'socket' event is still artificially set to emit onnextTick
when a ClientRequest is created.
This means in the following code the Scope will never be done because at least one tick needs
to happen before any matched Interceptor is considered consumed.const scope = nock(...).get('/').reply()const req = http.get(...)scope.done()
- Use to always emit a 'socket hang up' error. Now only emits the error if