Closed 3goats closed 1 year ago
This sounds like some kind of incompatibility between whatever provides the Go
class and node-fetch
?
Hmm yes - Since it works in the browser and with Deno, I'm not sure where to start looking.
There has been no activity on this issue for 3 years and it may no longer be relevant. It will be closed 1 month after the last non-automated comment.
There has been no activity on this issue and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.
What steps will reproduce the bug?
I'm importing a WebAssembly (WASM) component into my node app which is working to a point. However, the component needs to access the network to perform HTTP requests. Since the
fetch
API is not enabled I've installed thenode-fetch
module and made it available globally.However this is causing a kernel panic when the WebAssembly tries to connect. e.g.
This is the code I'm using for my test:
If I remove
node-fetch
you can see it's failing to connect. e.g.This works fine in a browser and also using deno. Not sure if its a bug or something I'm missing.
For reference, here is the deno code and output:
Output: