fix: update btoa boundary

[BBboy01]

Hi, as the description of btoa for unicode string from MDN, one byte is the range of btoa accept.

const testString = 'Í'
console.log(testString.charCodeAt())  // 205
console.log(window.btoa('Í')) // zQ==

[michaelficarra]

This looks correct. Can you add some test cases?

[BBboy01]

This looks correct. Can you add some test cases?

sorry for forgot this for so long, I just added the unit test with the range of whole 1 byte for atob and btoa

[davidchambers]

Thank you very much, @BBboy01! 👏

I updated the description of one test case to reflect the fact that btoa can now encode (some) non-ASCII characters. I also coalesced the new test cases. Are these changes okay with you, @BBboy01?

[BBboy01]

Thank you very much, @BBboy01! 👏

I updated the description of one test case to reflect the fact that btoa can now encode (some) non-ASCII characters. I also coalesced the new test cases. Are these changes okay with you, @BBboy01?

yeah. it's more semantic now.

[davidchambers]

I released this change as 1.3.0. Thanks again for the contribution, @BBboy01. 🍻