Unmatched requests get logged to the console.

[kentcdodds]

The lib/index.js file is built via webpack and has a console.warn in it in the match function from node-match-path:

/**
 * Matches a given url against a path.
 */
const match = (path, url) => {
    const expression = path instanceof RegExp ? path : pathToRegExp(path);
    const match = expression.exec(url) || false;
    // Matches in strict mode: match string should equal to input (url)
    // Otherwise loose matches will be considered truthy:
    // match('/messages/:id', '/messages/123/users') // true
    const matches = !!match && match[0] === match.input;
    console.warn('nmp', { path, url, match, matches  })
    return {
        matches,
        params: match && matches ? match.groups || null : null,
    };
};

But no version of node-match-path has a console.warn in it. Could we get a rebuild of this and a publish to get rid of that warning? It's kind of distracting 😅

Thanks!

[kettanaito]

Hello, @kentcdodds. Thanks for reporting this. My bad, I've published the library with some local version of node-match-path. Fixed in 0.9.1. Could you please update and let me know if it's fine? Sorry for any inconvenience this caused.

[kentcdodds]

No worries. I'll take a look tomorrow. Thanks!

[kentcdodds]

This is fixed. Thanks!

[bargar]

For anybody arriving here like me wanting to log requests, you can use this technique:

rest.get('*', (req, res, ctx) => {
  console.log(req.url.href)
  // Notice no `return res()` statement
})

The lack of return means that other handlers can still serve the request after it is logged.

[kettanaito]

Hey, @bargar! Thanks for posting this for others.

Note that MSW logs out requests that were matched, meaning their responses were mocked. However, you can see those requests and other requests in the "Network" tab of your browser. Sometimes extra logging to the console may not be necessary: just look into the "Network".

[bargar]

Thanks for posting this for others.

My pleasure.

you can see those requests and other requests in the "Network" tab of your browser

An excellent point for msw in the browser!

I probably should have mentioned that I was coming from the context of debugging a react testing library test run at the command line. The request logging alerted me to an unexpected request that I had neglected to mock with msw.