Michael Solomon
Michael Solomon
@marikaner If it happens for interceptors with the `replyWithError` function, you can make sure you throw an `Error` object.
@marikaner Interesting.. can you please send a reproducible code?
Could you provide more details to help me understand the issue better? What do you mean flaky? maybe it's another issue that should be addressed on its own?
@marikaner, maybe it's related to something we fixed on the `interceptors` side. Can you please try with [v14.0.0-beta.15](https://github.com/nock/nock/releases/tag/v14.0.0-beta.15)?
> I hope this doesn't count as spamming Feel free to put in any relevant info you find :) > However, I have good news: I was finally able to...
@marikaner This is what I get:  Maybe the custom sequencer causes some problems?
Thanks for verifying the fix! I'll open a PR.
@andreainnocenti As a workaround, can you try wrapping the object with `Error`? ```js const errorData = { code: 123, message: "Something went wrong" }; const err = new Error(errorData.message); err.data...
Hey all :) I looked into this issue more. Why does `replyWithError` support plain objects? I haven't used this function myself, but I understand its purpose is to mimic some...
How does the code pass the check [for an already applied interceptor](https://github.com/mswjs/interceptors/blob/main/src/Interceptor.ts#L82)? It seems like this is the problem we need to solve.