JSON response with special chars truncated since 2.2.0 about msw HOT 3 CLOSED

I left a comment in #1658 but as this is the same problem with mine, I'll copy it here.

I have an issue with 2.2.0+ version of MSW, when I put CJK(Chinese, Japanese, Korean character) in MSW response.
Until [email protected], it was fine. I checked out what was changed in 2.2.0, and I found this commit could be the problem.

For example, the length of string '조현영' (which is Korean) is 9 bytes in network, whereas 'abc' is 3 bytes. But both are 3 lengths in JavaScript. I think current implementation which calculate length by just string.length can be problem.
I think using new TextEncoder().encode(str).length would be better to calculate Content-Length. Thank you

from msw.

Root cause

Right now, we are relying on the string length to determine the value of the automatic Content-Length response header.

Instead, we should convert the string to buffer and measure its byte length. There are a couple of ways to do that:

1. new TextEncoder().encode(text).byteLength
2. new Blob([text]).size

Pull requests are welcome! I'd start with a failing test for special characters right here:

from msw.

Released: v2.2.2 🎉

This has been released in v2.2.2!

• 📄 Release notes
• 📦 npm package

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.

from msw.