onUnhandledRequest: Throws an exception when using the "error" strategy

[kettanaito]

GitHub

• Fixes onUnhandledRequest: throw error should fail test #855
• Related to Show onUnhandledRequest: 'error' in stdout and fail tests #539

Changes

• When the "error" strategy of the onUnhandledRequest option is used, any request that has no matching request handler will throw an exception to halt request processing and fail any code dependant on it:

await fetch('https://api.com/unhandled')
// FethError: ...

• The developer-friendly console.error is preserved because the message is too verbose to be used as the FetchError reason. Instead, the fetch error reason is a compact summary of why the request failed (cannot be performed as-is).

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit b403936:

Sandbox	Source
MSW React	Configuration

[vai0]

Thank you for this amazing library. Does throwing an error also stop tests that depend on setupWorker()?

[vai0]

Thank you for this amazing library. Does throwing an error also stop tests that depend on setupWorker()?

Answered my own question - it does.