-
Notifications
You must be signed in to change notification settings - Fork 10
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
Remove node-fetch and its typings #67
Conversation
Can't we replace this with the native fetch api node introduced? |
Some distros don't make it easy to use a recent nodejs, but if we require a recent nodejs for other features anyway we can switch to builtin fetch. Are there any benefits from using the builtin fetch vs node-fetch 2? |
Not really sure to be honest, and personally I just use Docker so node versions don't affect me much. So I'm fine with whatever you wanna do. |
Just tested and node 18 has native fetch, so the module shouldn't be necessary anymore |
84968a3
to
23a13fd
Compare
23a13fd
to
91a4ce1
Compare
No longer necessary given the native fetch function now available in node 18.
91a4ce1
to
e2b25b2
Compare
All good now, this is now a 'yeet node-fetch' PR |
I assume this is tested? |
// test.js
fetch("https://github.com/CivPlatform/map-sync/pull/67")
.then((res) => res.text())
.then((txt) => console.log("SUCCESS!"))
.catch((err) => console.error("Err!", err))
|
Good enough for me! |
No description provided.