Handle non-buffer binary data in node

[cortopy]

The difference between browser and node generally works well. However, there are some instances in which the boundaries are not that clear. For example:

• Jest runtime that loads jsdom in the background
• Server side rendering of single-page applications (that may also rely on some kind of DOM implementation in node to simulate a browser-like environment)

I bumped into this issue when testing attachments in my application. I believe these changes fix the issue.

Apologies for not adding any tests. This is my first contribution and for what I can see, node tests are run with mocha and browser tests with a headless browser.

If tests are required, I can add them but I'd need to know which would be the best way of replicating those two use cases above in current tests setup. Any help in this regards would be much appreciated

[janl]

we’d need tests, and no CI build failures :)

[dheimoz]

hello @cortopy would you like to have your contribution reviewed? Tests have been migrated to Github Actions.

[AlbaHerrerias]

Hey @cortopy, could you rebase from master? It will allow me to trigger Github actions. Thanks!

[alxndrsn]

No action for 5 years.