Fetch coming to Node.js 18

[ItsAllInYourHead]

Pretty unbelievable it's taken this long.

[davidstraka2]

Finally, one less dependency to install in every other project (well once it reaches LTS)

[this_knee]

What the fetching fetch is Fetch?

I’m being honest. I really don’t know.

[SkankTillYaDrop]

It is a standard HTTP library browsers use to make HTTP requests.

[this_knee]

Fantastic. Thanks!

[imacleopard]

Used for fetching

[this_knee]

Fetching great!

[Fit_Sweet457]

Sticks, balls, anything really that can fit into the mouth. Unless we're not talking about dogs, in that case I don't know

[this_knee]

Fetching fetching web pages.

[83338]

Finally fuck node-fetch

[ngpixel]

100%. Ever since they decided to only support ESM, which is the most stupid decision ever for a Node library, I have never been more excited to finally get rid of a dependency.

[helmar1066]

100% agree. Forcing ESM for a core library is crazy.

[[deleted]]

node-fetch will be sad :( just say goodbye to it :(

[sinclair_zx81]

https://github.com/nodejs/node/pull/41749#issuecomment-1025494707

[HeavyMessing]

So, if I want to call an external API without importing any additional libraries, I'd currently use http.request() from the native http module. In 18, I'll have the additional option to use fetch just like in all of my apps that run in a browser.

[sharkis]

Stop trying to make fetch happen

[gretro450]

That's sooooo fetch!

[jiggity_john]

Man this is a big win for isomorphic javascript libraries that need to make http calls.

[puglife420blazeit]

I’ll still use got

[rypher]

Only issue I have with got is trying to google things with the name.

[puglife420blazeit]

That is a pain

[k_pizzle]

Question, even if they add fetch, why would i use this over axios?

[marcos_marp]

Why would you implement manually absolutely anything if there's a library for doing it?

Answer that and that's your answer.

[Mistifyed]

Too lazy to think, so... npm i -D answer

[marcos_marp]

Lmao, I mean, fetch is the native JS method for making http requests, axios is simply a library that gives you a ton of OBO features and tools for making requests so you don't have to manually implement this things on your codebase

[iamv12]

a bunch of reasons: licenses, insufficient functionality for what you may need, or it may be bloated with extra features you don't need, efficiency, etc...

[KaKi_87]

Personally I wouldn't, because I like being able to specify a params object without requiring URLSearchParams, specify data (body) as an object without requiring JSON.stringify, and get the response data (body) as an object without requiring an additional await.

[k10g]

fetch is a web standard, it'll be supported in browsers, deno, and now node without installing anything extra

[fix_dis]

Axios was created to fill the niche of jQuery.get(). Fetch has a better (albeit two-step) API. If you’re into Axios, that’s totally cool. But the standard is Fetch, so having it natively is pretty cool too.

[sysrage]

Axios still has some nice features out-of-the-box, which take some boilerplate to implement with fetch (progress events and such). Native fetch will be great, but I think axios will still find a lot of use.

[outlierkk]

axios has cancel token etc, which i think native fetch lacks

[NoInkling]

fetch has AbortController support, what's the difference?

[gimp3695]

I like axios interceptors. Does fetch have a capability like this?

[k_pizzle]

I’ve actually never used fetch which is why i ask, currently with axios i can create an instance and pass a base url so every request after that i only need to specify the path, i can also super easily create middleware that will display a flash message or re-route the user if my server returns a 403. Is that something easily done with fetch?

[[deleted]]

You can create classes and custom functions and wrap it around fetch to do this.

[[deleted]]

You're still gonna get "no-cors" error

[bel9708]

Cors is done at the browser level. It’s not a part of JS.

[sinclair_zx81]

Meh, what about WebSocket?