[email protected] axios change causes issues in Chrome Extension

[IgorShadurin]

We've run into an issue with the recent update (version 6.0.0) of your library. The change from ky to axios for handling HTTP requests resolved some issues we were facing with web apps in the browser. However, it seems to have introduced a new problem for our Blossom Chrome extension (https://github.com/fairDataSociety/blossom).

We're now getting the error Adapter 'http' is not available in the build. After some research, I found related issues on axios's GitHub and StackOverflow:

• Axios doesn't work on edge runtime, Adapter 'http' is not available in the build axios/axios#5523
• https://stackoverflow.com/questions/66305856/typeerror-adapter-is-not-a-function-error-when-using-axios-and-webpack-in-chrome

As far as I understand, we could potentially solve this issue by:

• Replacing all axios HTTP requests with fetch.
• Allowing the pass of custom adapters to axios, like the one offered here: https://www.npmjs.com/package/@vespaiach/axios-fetch-adapter

That said, these solutions might not be the most elegant or efficient for our use case. We would appreciate it if you could look into this issue and provide guidance or an alternative solution.

Thank you for your time and assistance.

[bee-worker]

Release v6.1.0 addresses this.

[IgorShadurin]

What is the process now to get bee-js working in Chrome Extension?
Tried to substitute adapters from links above, still throws the same error.
@Cafe137