`.finally()` is not a function
See original GitHub issueThis issue appears to be an upstream issue with node-fetch
with it’s home grown promises, but this does cause errors with when attempting to use this library with others that do expect .finally()
to exist.
It seems that the next version of node-fetch
will support promises, so that is worth keeping an eye on.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
api.get(...).then(...).catch(...).finally is not a function
finally() doesn't supported by all of browsers. To ensure my code works on the all browser, i always use .catch() followed by .then()...
Read more >Promise.prototype.finally() - JavaScript - MDN Web Docs
The finally() method of a Promise object schedules a function to be called when the promise is settled (either fulfilled or rejected).
Read more >Error finally is not a function #56 - Vizzuality/layer-manager
In happens in Firefox 68.0.1 64-bit. It is happening in all projects based on create-react-app (webpack, babel an react). ... I open this...
Read more >Firefox Promise - getting finally is not a function? : r/javascript
Hello all, According to https://caniuse.com/#search=finally and…
Read more >JavaScript Promise finally()
In this tutorial, you will learn how to use the JavaScript Promise finally() method to execute the code once the promise is settled....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Let’s wait for the full release. It seems like they’ve been in pre-release mode for a long time. I’d feel safer waiting for the final one
Thanks for the heads up. When the new version of
node-fetch
is released, would you be up for creating a PR to upgrade?