We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'd be happy to propose a PR, but I'd recommend rewriting the transport with fetch instead of extending the current approach:
sdk-javascript/src/transport/http/index.ts
Line 49 in db60220
... As I'd have to use setTimeout(), which would make the code more complicated.
setTimeout()
The drawback of fetch() is that it'd require Node.js 18+. Which shouldn't be too bad as Node.js 16 is reaching EOL in a few weeks.
fetch()
The text was updated successfully, but these errors were encountered:
@gnarea feel free to submit a PR 👍
looks like the exact date it the 11th of September for node 16 EOL, so probably wouldn't merge until then
Sorry, something went wrong.
This issue is stale because it has been open 30 days with no activity.
No branches or pull requests
I'd be happy to propose a PR, but I'd recommend rewriting the transport with fetch instead of extending the current approach:
sdk-javascript/src/transport/http/index.ts
Line 49 in db60220
... As I'd have to use
setTimeout()
, which would make the code more complicated.The drawback of
fetch()
is that it'd require Node.js 18+. Which shouldn't be too bad as Node.js 16 is reaching EOL in a few weeks.The text was updated successfully, but these errors were encountered: