Closed Yaswanth-Tippireddy closed 3 years ago
This problem exists only in isomorphic-fetch@2
, which depends on node-fetch@^1.0.1
. I don't know if isomorphic-fetch@2
is still actively supported... However, the latest version of this package is isomorphic-fetch@3
, which depends on node-fetch@^2.6.1
and doesn't have this problem. So, probably the top suggested fix is to upgrade to isomorphic-fetch@3
.
https://www.npmjs.com/advisories/1556
The dependency on older version of node-fetch has been breaking some packages.