Preserve the original request URL in "onUnhandledRequest" warnings

[kettanaito]

Prerequisites

• I confirm my issue is not in the opened issues
• I confirm the Frequently Asked Questions didn't contain the answer to my issue

Environment check

• I'm using the latest msw version
• I'm using Node.js version 18 or higher

Node.js version

v20.11.0

Reproduction repository

Always specify repros. Don't follow my lead.

Reproduction steps

1. Set up MSW in the browser.
2. Configure the onUnhandledRequest callback:

await worker.start({
  onUnhandledRequest(request, print) {
    console.log('URL:', request.url)
    if (/\.(css|js|json|png|jpg|gif)$/.test(request.url)) {
      return
    }

    print.warning()
  },
})

3. Make a request like /fo/bar/?t=123

Current behavior

MSW prints a clean URL, making it hard to understand why my custom onUnhandledRequest logic is not matching this request:

Expected behavior

MSW preserves the unhandled request URL as-is, which includes keeping its query parameters and fragments.

[kettanaito]

How to fix this

The fix would be right here:

msw/src/core/utils/request/onUnhandledRequest.ts

Line 25 in e83a669

const publicUrl = toPublicUrl(url)

The reason we use toPublicUrl() here is to omit the document's origin and print a relative URL. There are two ways to fix this:

1. Always print an absolute URL. I.e. remove toPublicUrl and rely on request.url as-is.
2. Still get a potentially relative URL but copy the search and fragment from the original request.url (we construct a URL instance out of it anyway).

[nagadevkrishna]

Hi, I made a change and raised the PR: #2128

[kettanaito]

Released: v2.2.14 🎉

This has been released in v2.2.14!

• 📄 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.