"Error: Nock: No match for request" How to quickly understand what doesn't match?

I often face this error (Error: Nock: No match for request) using Nock, but I find it hard to quickly understand what doesn’t match in order to adjust.

I used to use nock(apiUrl).persist().log(console.log)(link) that was doing the job pretty well. But it’s been deprecated and I’ve recently updated the dependancy. Therefore I need to adapt, yet I find it hard to grasp what info is interesting for my debugging.

How to get something similar to Jest, obviously comparing what was expected, and what was actually called for quick and straightforward debugging ?

29 thoughts on “"Error: Nock: No match for request" How to quickly understand what doesn't match?”

  1. Greetings from California! I’m bored to tears at work so I decided to check out your site on my iphone during lunch break. I love the information you present here and can’t wait to take a look when I get home. I’m surprised at how fast your blog loaded on my cell phone .. I’m not even using WIFI, just 3G .. Anyhow, great site!

    Reply

Leave a Comment