TypeError: Expected signal to be an instanceof AbortSignal

[anwbfvr]

We experience a bug in node-fetch in relation to minifying code: node-fetch/node-fetch#784 when using @jsforce/[email protected]

The bug is fixed in node-fetch@3 (according to node-fetch/node-fetch#784 (comment)), so updating the dependency of node-fetch might help.

[cristiand391]

We explored the upgrade path from node-fetch v2 -> v3 for jsforce a few weeks ago and decided we'll stay on node-fetch v2 for jsforce v3.

I'll post the details later post GA, but a few things that blocks us from using node-fetch v3 are:

• it's an ESM module jsforce is still CJS (there will be an ESM build but we don't plan to keep different branches just for these).
• dropped support for usage in browsers

Also, now node has native a fetch we want to explore dropping node-fetch and just use the nativefetch in node and browsers (probably in the jsforce v4 roadmap).

[john-bflow-mcgowan]

@anwbfvr did any of the workarounds in the linked node-fetch issue resolve your issue? I'm also running into this issue deploying my code with jsforce 2.0.0

[anwbfvr]

@anwbfvr did any of the workarounds in the linked node-fetch issue resolve your issue? I'm also running into this issue deploying my code with jsforce 2.0.0

Yes, we are now using https://esbuild.github.io/api/#keep-names