Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(Safari): send explicit null response bodies #1833

Merged
merged 1 commit into from
Nov 4, 2023

Conversation

* @see https://github.com/mswjs/msw/issues/1827
*/
const responseBufferOrNull =
response.body === null
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here's the actual fix.

@kettanaito kettanaito merged commit 66fb437 into main Nov 4, 2023
9 checks passed
@kettanaito kettanaito deleted the fix/1827-safari-empty-array-buffer branch November 4, 2023 14:41
@kettanaito
Copy link
Member Author

Released: v2.0.3 🎉

This has been released in v2.0.3!

Make sure to always update to the latest version (npm i msw@latest) to get the newest features and bug fixes.


Predictable release automation by @ossjs/release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Safari readableStreamTransfer workaround turns null body into empty ArrayBuffer, requests fail
1 participant