Well, I've seen a similar issue before, and it turns out that it was related to the node-fetch version, please check this topic reply.
Well, I've seen a similar issue before, and it turns out that it was related to the node-fetch version, please check this topic reply.