Drop request parsing from "onUnhandledRequest"

[kettanaito]

Scope

Improves an existing behavior

Compatibility

• This is a breaking change

Feature description

Right now, we parse any unhandled request just to see if it's not a GraphQL request. We do that to provide a bit better developer experience by including the operation type and name in the unhandled request warning message.

However, because of this, everybody ends up with all GraphQL dependencies even if they are not mocking anything GraphQL related. This has also been reported to end up with a lot of additional modules imported when using MSW (by @thepassle).

Solution

• Remove request parsing from onUnhandledRequest at all.
• Log out request method and path. This is sufficient to help the developer debug what's unmatched.
• In the future, we can log out the request initiator, once we implement it (Show unhandled request's initiator #1764)

[kettanaito]

As a part of this change, we may also consider doing #1599 to gain an even bigger performance boost for unhandled requests.

[kettanaito]

Released: v2.1.4 🎉

This has been released in v2.1.4!

• 📄 Release notes
• 📦 npm package

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

---

Predictable release automation by @ossjs/release.