fix: use dynamic import for node-specific libraries

[kanadgupta]

🧰 Changes

I went down a little rabbit hole to see how it would work to load these SDKs in a browser environment as part of the docs I want to write up. The closest I got to success was this error (even with a webpack config and various tweaks to it):

Looks like the same error alluded to here: #604 (comment)

I figured that by only loading the node-specific libraries within the function that needs it, we might be able to successfully run this in a browser environment?

🧬 QA & Testing

I was unable to successfully npm link this into my setup in a way that played nicely with webpack so hard to see if this will work. Open to other ideas here!

[kanadgupta]

Update: chatted with @erunion about this a while back and we might be able to bring in the datauri methods that we use directly — will pick this up when I have capacity again!

[joaocanaverde-blue]

@kanadgupta @erunion Hi! Any chance this can be merged? Happy to contribute if anything is needed.

[kanadgupta]

@erunion ready for review again. I tried playing around with vendoring datauri but it felt like overkill since we'd need to create a separate subpackage for it since it's used in both core and testing-utils

[kanadgupta]

Hi there @joaocanaverde-blue — v7.0.0-beta.11 includes this change.

[joaocanaverde-blue]

@kanadgupta thank you! 🚀