feat: support UInt8Array in place of Buffer

[kylecarbs]

This seems reasonable, considering memfs supports the browser, and users are more likely to have instances of Uint8Array there.

Resolves #733

[G-Rath]

I feel like this probably is a fix for #733 - would you mind double checking that for me, and throwing in a test or two as/when you think is needed? (if you don't think it's worth having any, I'm ok with that too 🙂)

[kylecarbs]

@G-Rath seems to fix #733! I added tests before, but they don't do much - the structure is the same for Uint8Array. I'm happy to add it if you'd prefer, though!

[G-Rath]

Awesome! Mind sticking a "resolves" line to your description?

Re tests it doesn't surprise me but would still be good if we had at least one where were explicitly passing in a Uint8Array

[kylecarbs]

@G-Rath added to the description! I can add one before merge - no biggie.

[kylecarbs]

@G-Rath fixed. I also removed a debugger; line that was causing me some issues, just assuming that's fine.

[kylecarbs]

Seems like there are some unrelated flakes failing - but test I added should be good.

[G-Rath]

I also removed a debugger;

Yeah that should never have been landed - I've opened #1086 to remove it and another from a test, just so we've got a dedicated changelog entry as it's a whole bug of its own

Seems like there are some unrelated flakes failing

A couple of the watch ones are very slightly flakey, but thankfully only slightly so yes after rerunning you've got green across the board 🎉

[github-actions]

🎉 This PR is included in version 4.16.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀