-
I am trying to setup test cases with `jest`, but after the test was finished the process will stalled and does not exit.
Using the command `jest --detectOpenHandles` will show this error message …
-
### Please avoid duplicates
- [X] I checked [all open bugs](https://github.com/nock/nock/issues?q=is%3Aissue+is%3Aopen+label%3Abug) and none of them matched my problem.
### Reproducible test case
N…
-
when trying to use presets
-
`interceptors` expects the error to be from type `Error` in [`handleRequest`](https://github.com/mswjs/interceptors/blob/472bcbe4b6b7f0652da10eb647a3aaa898ad4f7c/src/utils/handleRequest.ts#L47), which…
-
### Describe the bug
Hi there. I'm using [`nock@beta`](https://github.com/nock/nock/tree/beta) and it is no longer able to intercept requests from this library when using the default Node.js `httpC…
-
The mentioned package is not present in NPM
"npm i @mswjs/socket.io-binding"
results in
```
'@mswjs/socket.io-binding@*' is not in this registry.
```
-
It would be great if the starter can support mock for graphql like here - https://mswjs.io/docs/network-behavior/graphql
-
Currently there are no tests, some options:
- React Testing Library via Jest or Vitetest
- Cypress for e2e
- Playwright (most interesting solution https://github.com/vercel/next.js/blob/canary/packag…
-
- [x] should be safe to call in the middle of a request
- [x] socket emits `connect` and `secureConnect` events @kettanaito (edge case - https://github.com/mswjs/interceptors/pull/515#issuecomment-20…
-
When using ClientRequestInterceptor with ProxyAgent, it ends with error
TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"
at new ClientRequest (node:_http_clie…