Skip to content

Tags: Uzlopak/nock

Tags

v13.3.4

Toggle v13.3.4's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix(typescript): support `nock(new URL('https://example.test/'))` (no…

…ck#2526)

v13.3.3

Toggle v13.3.3's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix: revert nock#2350 (Push persisted interceptors to the end instead…

… of ignore on remove) (nock#2511)

This reverts commit 8aab603.  See nock#2500

v13.3.2

Toggle v13.3.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix: `nock.removeInterceptor` can remove the wrong Intercept (nock#2497)

v13.3.1

Toggle v13.3.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix: update Socket for Node 18 compat (nock#2467)

In Node 18+, Write Stream detection has changed. We needed to add a dummy `write` method to our `Socket` class in order to avoid the following error:
> The "stream" argument must be an instance of ReadableStream, WritableStream, or Stream. Received an instance of Socket

The minimum requirements for SSL certs also increased, so I was forced to update our certs used in testing.

v13.3.0

Toggle v13.3.0's commit message

Partially verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
feat: support for WHATWG URLs (nock#2437)

Co-authored-by: Ryan Wheale <[email protected]>
Co-authored-by: Matt R. Wilson <[email protected]>

v13.2.9

Toggle v13.2.9's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix(README): Add notes about Scope vs Interceptor matchHeader calls (n…

…ock#2382)

v13.2.8

Toggle v13.2.8's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix(types): allow regexp on `Definition#scope` and `Definition#path` (n…

…ock#2374)

v13.2.7

Toggle v13.2.7's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix: `InterceptedRequestRouter.handleWrite` arity issue (nock#2371)

v13.2.6

Toggle v13.2.6's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Revert "chore(deps-dev): bump got from 11.8.3 to 12.1.0" (nock#2366)

This reverts commit 8a82b50.

v13.2.5

Toggle v13.2.5's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix(dep): migrate from lodash.set to lodash. (nock#2306)

Listing `lodash` as a prod dependency has a few advantages over the single func dep we were using.
Primarily, when a security vulnerability is patched in LoDash, those changes don't get published to individual function libs anymore.
The most recent example being the prototype pollution that was patched in 4.17.16.
That particular vulnerability didn't effect Nock because of our usage, however, Nock does show up as having a vulnerability because of it which is a pain for consumers. It also creates a future problem where the next patch could affect Nock more directly.
nock#2279

It should be noted that LoDash itself discourages the use of these single function libs: https://lodash.com/per-method-packages

This changes also removes the vendor-izing of two LoDash functions in favor of using the lib directly (`isPlainObject` and `mapValues`).