Empty URL in resolver.
See original GitHub issueDescribe the bug
I spent a lot of time to get why my url don’t mock. The reason is empty URL.
im sending request to /dev/api/v1/auth/login but console.log(req.url) show in terminal empty URL {} object:
Environment
msw: 0.21.3
nodejs: 14.14.0
npm: 6.14.18
Please also provide your browser version. Im using JEST tests. There is no browser running.
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (12 by maintainers)
Top Results From Across the Web
angular - Activated Route URL Always Empty - Stack Overflow
Every time the route changes, the console.log() triggers. But, no matter what the route, the value is always "" (empty string). What is...
Read more >Base URL malformed or empty - Sitebulb
Base URL malformed or empty. This means that the URL in question contains a base URL which is malformed or empty. Why is...
Read more >Empty Url Segment in Route Template - MSDN - Microsoft
Im having an issue defining the correct route template to handle an request with an emtpy url segment. Either that or this is...
Read more >2.6 URLs — HTML5 - W3C
A string is a valid non-empty URL potentially surrounded by spaces if, after stripping leading and trailing whitespace from it, it is a...
Read more >What should a link resolver do when a document type ...
I think it would be good if link resolvers could return null (or undefined , whatever you prefer) in cases where there is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It works! Thank you! I close issue.
One of the contributors has discovered an issue in
node-request-interceptor
, when we didn’t inherit the default hostname in certain scenarios (https://github.com/mswjs/node-request-interceptor/pull/64). This would also cause a URL likehttp://undefined
. Let’s keep this in mind until we receive a confirmation from the author on the URL validity on his side.