Zach Newton

Yes absolutely. The reason for switching to fetch was that Axios doesn't provide streaming capability which was something we wanted to experiment with. Unfortunately, the choice to use `node-fetch` was...

@malekpour Upgrading to node-fetch v3 would impact everywhere else in the repo that uses node-fetch. If what @curtisman says is true, then our use of node-fetch v2 is important for...

According to cross-fetch README, > Just like isomorphic-fetch, it is just a proxy. If you're in node, it delivers you the [node-fetch](https://github.com/bitinn/node-fetch/) library, if you're in a browser or React...

In the [section of the `node-fetch` upgrade guide](https://github.com/node-fetch/node-fetch/blob/main/docs/v3-UPGRADE-GUIDE.md#dropped-the-browser-field-in-packagejson) that @curtisman linked to, they seem to recommend using `cross-fetch` "if you are using node-fetch client-side". Switching the r11s-driver to `cross-fetch` would...

Merged #9433 to resolve the immediate issue that r11s-driver does not work without host adding their own Node polyfills. Opened #9443 to track improvement of the solution so that we...

This would be super helpful! We have a lot of pages setting `document.domain` to support iFrames, but we are also trying to add support for the webcomponent implementation of our...

Re-opening with expanded scope

Not sure if I missed this in the above discussion, but this change will mean that NGINX re-routing of Alfred socket endpoints to Nexus will be a requirement to ensure...