When using an object with "response" on replyWithError the output always returns undefined

[Hugo01]

What is the expected behavior?
When using "nock('url').replyWithError({response: 'error"})"
console.log(error.response) should print ("error")

What is the actual behavior?
error.response is undefined

How to reproduce the issue

1. Create a function

const function = () => {
  try {
    ....
  } catch (err) {
    console.log(err.status)
    console.log(err.response)
  }
}

2. Create a test using that function

it('Test function', async () => {
    const wrapper = mount(Login)
    const { vm } = wrapper
    nock('http://localhost:3000')
      .post('/auth/login')
      .replyWithError({
        response: 'error',
        status: 400
      })
     await expect(vm.function()).rejects.toThrowError('error')
  })

 console.log(err.response) from the component above outputs "undefined" instead of "error"
 console.log(err.status) works correctly, the ouput shows "400"

Versions

Software	Version(s)
Nock	^13.1.4
Node	>= 12.22.1

[gr2m]

could you share a code example with all code needed to run it? Here is a great example: https://runkit.com/fluggo/nock-nock-2197

[kmcdon10]

I just ran into this issue as well, but then I figured out that if you set the value of the response to contain an object with metadata, it was no longer an issue.

it('Test function', async () => {
    const wrapper = mount(Login)
    const { vm } = wrapper
    nock('http://localhost:3000')
      .post('/auth/login')
      .replyWithError({
        status: 400,
        response: { data: { detail: { error_reason: 'insert issue here' } } }
      })
  })

 console.log(err.response) is no longer undefined

[antowkabond]

I have the same problem

@kmcdon10 is it working for you? Which version are you using?

[tduyng]

There is no update on this? I have same problem too.

[mikicho]

This test passes. Do you still have this problem?

[mille-printemps]

@mikicho Would it be possible for you to tell us which version of nock and node you are using?

I had the same issue described here, and I am wondering what makes these differences.

[mikicho]

@mille-printemps probably Node 20 and nock latest

[mille-printemps]

@mikicho
Thank you for the reply. Eventually, I found a workaround of this issue in my test case. I appreciate your response.

[mikicho]

@mille-printemps What is the workaround? maybe it will help to understand the root cause.

[mille-printemps]

@mikicho
Okay, I am not really sure if this is helpful. I will try to explain my case.

I was using superagent as an http client and tried to mock it using nock. It seems that superagent throws ResponseError when the HTTP status is 4xx and 5xx. The definition of ResponseError is here.

In order to check if the object caught in catch clause is ResponseError, I implemented a type guard and I also needed to check if response and response.body in ResponseError were undefined in my case.

In order to test this, I tried to use replyWithError() with a parameter like {status: 400, response: {body: {...}}}. However, response was always undefined and that was the issue.

It turned out that I used reply() like reply(400, {...}) and it solved my issue. So I found that the data passed to replyWithError() as response.body was the same as the data passed to reply() as the second argument.

HTH.