Bypassed requests made to the firebase emulator result in a timeout
See original GitHub issueDescribe the bug
Bypassed requests made to the firebase emulator result in a timeout.
Environment
msw: 0.27.0
nodejs: 15.0.1
npm: 7.0.3
jest: 26.0.1
To Reproduce
Expected behavior
Requests made to the firebase emulator should bypass msw entirely, and succeed.
Additional information
I’ve tried also supplying handlers which should still result in msw being bypassed, per https://github.com/mswjs/msw/issues/234#issuecomment-646869533.
Might be that this is tied to #414.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Timeout error always occurs when tried to test firestore ...
In your createAuthApp() function, you are initialising the test application with a project ID of RULES_PATH but in your tests you are ...
Read more >Test your Cloud Firestore Security Rules - Firebase - Google
Every database request from a Cloud Firestore mobile/web client library is evaluated against your security rules before reading or writing any data.
Read more >Set up Android Emulator networking
The emulator provides versatile networking capabilities that you can ... and a connection through a proxy result in different GET requests.
Read more >Meet the Firestore Emulator Requests Monitor
You can access the Requests Monitor right now from the Emulator UI if you have the latest Firebase CLI running. (If not, it's...
Read more >Firebase Emulators Error: TIMEOUT: Port 8080 on localhost ...
This timeout issue happens when you try to run Firebase emulators locally. Assuming you've run firebase init and installed the emulators as soon...
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
I have opened a PR here that should resolve this issue
I didn’t see that the issue was for
setupServer
. I have updated now my PR and it seems fixed for the browser. I’ll check on node what is happening