-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node-fetch v3 is out #115
Comments
Fetch implementations that run on Node shouldn't force ESM on end users/developpers. Using ESM in Typescript or older projects is not easy and will break things. It's just not worth it at this time. As a side note: fetch is coming to node so there is really no hurry in breaking everything... |
@israelidanny as pointed out by @p-j , v3 has just been released and node-fetch is facing a lot of issues for being an ESM only lib (see link provided by him). I feel it would be prudent to monitor how that discussion unfolds before taking any actions. @p-j re: your side note, unfortunately we can't firmly state that fetch is coming to node. Although the API has been merged into |
Even if |
@Lioness100 so far I don't see a good reason to replace |
Is it time to update?
The text was updated successfully, but these errors were encountered: