fix(fetch): do not print console error on request failures

[azangru]

Fixes #381

Description

Currently, when a network error is simulated in a response from msw server, as described in the docs, (`return res.networkError('Failed to connect')), an error message with a stack trace appears in the console, although the tests would pass.

Here is an example of how this would look like to the developer who is using msw:

An error message, despite passing tests, is distracting. This PR removes the console.error statement responsible for this output.

When checked locally, this change cleaned up the test log:

[kettanaito]

Thanks for fixing this, @azangru. I think this is a move for the better. Will wait for the build to pass and then will merge.

[kettanaito]

The CI reported that the browser test for fetch exceptions was still expecting the error to be printed in the console:

  1) [chromium] › modules/fetch/fetch-exception.browser.test.ts:3:5 › treats middleware exceptions as TypeError: Failed to fetch 

    Error: expect(received).toEqual(expected) // deep equality

    - Expected  - 3
    + Received  + 1

    - Array [
    -   "GET http://localhost:3001/resource net::ERR_FAILED",
    - ]
    + Array []

      38 |     },
      39 |   })
    > 40 |   expect(errors).toEqual(['GET http://localhost:3001/resource net::ERR_FAILED'])
         |                  ^
      41 | })
      42 |

I've adjusted the expectations here and pushed the changes. Rerunning the tests...

[kettanaito]

Welcome to the contributors, @azangru 🎉

[kettanaito]

Released: v0.22.16 🎉

This has been released in v0.22.16!

• 📄 Release notes
• 📦 npm package

Make sure to always update to the latest version (npm i @mswjs/interceptors@latest) to get the newest features and bug fixes.

---

Predictable release automation by @ossjs/release.