Replies: 1 comment
-
|
Thanks, we will look into. Waiting for axios to fix this seems to be a good option, we keep the dependencies up to date anyway! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
For fast prototyping we wanted to use Cloudflare workers which should speak to the enmeshed connector. However since the TypeScript SDK uses axios it cannot be used inside a Cloudflare worker since it only supports the fetch API (see axios#2507 and axios#1219). There are problems reported with NextJS and Amazon AWS as well. However for the next version of axios (see axios#4209) a fetch-based adapter might be implemented (see trello board -> fetch based adapters are "Potential issues to be added"). I had a look into the SDK and I see some workarounds:
HttpClientsimilar toAxiosInstancewith only the methods which are actually used by the SDK. Now there could be aFetchHttpClientandAxiosHttpClient. Consumers can decide which of both they want to use.In our case it is a low priority issue. For accessing the enmeshed connector we will use a dedicated micro service running in its own docker container so that we will not have this issue. That's also the reason why I haven't created a feature request. However I wanted to document this somewhere. So other developers will not get the same error as we did.
Beta Was this translation helpful? Give feedback.
All reactions