Modern Node.js Patterns

Post by freeopinion » Mon, Aug 04, 2025, 1:30 AM UTC

tanduv wrote: post #78

farkin88 wrote: post #16

The killer upgrade here isn’t ESM. It’s Node baking fetch + AbortController into core. Dropping axios/node-fetch trimmed my Lambda bundle and shaved about 100 ms off cold-start latency. If you’re still npm i axios out of habit, 2025 Node is your cue to drop the training wheels.

I never really liked the syntax of fetch and the need to await for the response.json, implementing additional error handling - async function fetchDataWithAxios() { try { const response = await axios.get('https://jsonplaceholder.typicode.com/posts/1'); console.log('Axios Data:', response.data); } catch (error) { console.error('Axios Error:', error); } } async function fetchDataWithFetch() { try { const response = awa…

  fetch(url).then(r=>r.ok ? r.json() : Promise.reject(r.status))
  .then(
    j=>console.log('Fetch Data:', j),
    e=>console.log('Fetch Error:', e)
  );

Post by stevage » Mon, Aug 04, 2025, 1:32 AM UTC

farkin88 wrote: post #47

franciscop wrote: post #43

Earlier quoted context omitted.

As a library author it's the opposite, while fetch() is amazing, ESM has been a painful but definitely worth upgrade. It has all the things the author describes.

Interesting to get a library author's perspective. To be fair, you guys had to deal with the whole ecosystem shift: dual package hazards, CJS/ESM compatibility hell, tooling changes, etc so I can see how ESM would be the bigger story from your perspective.

Post by panzi » Mon, Aug 04, 2025, 1:39 AM UTC

kaoD wrote: post #115

panzi wrote: post #84

Unless it changed how NodeJS handles this you shouldn't use Promise.all(). Because if more than one promise rejects then the second rejection will emit a unhandledRejection event and per default that crashes your server. Use Promise.allSettled() instead.

This didn't feel right so I went and tested. process.on("uncaughException", (e) => { console.log("uncaughException", e); }); try { const r = await Promise.all([ Promise.reject(new Error('1')), new Promise((resolve, reject) => { setTimeout(() => reject(new Error('2'), 1000)); }), ]); console.log("r", r); } catch (e) { console.log("catch", e); } setTimeout(() => { console.log("setTimeout"); }, 2000); Produces: alvaro@D…

Post by drewbitt » Mon, Aug 04, 2025, 1:58 AM UTC

jameshart wrote: post #116

Our_Benefactors wrote: post #100

Earlier quoted context omitted.

What, surely you’re not implying that bangers like the following are GPT artifacts!? “The changes aren’t just cosmetic; they represent a fundamental shift in how we approach server-side JavaScript development.”

And now we need to throw the entire article out because we have no idea whether any of these features are just hallucinations.

Post by drewbitt » Mon, Aug 04, 2025, 2:02 AM UTC

jiggawatts wrote: post #129

MuffinFlavored wrote: post #121

Earlier quoted context omitted.

> ASP.NET Core is a very good choice too. I have found this to not be true.

Recently? In my experience ASP.NET 9 is vastly more productive and capable than Node.js. It has a nicer developer experience, it is faster to compile, faster to deploy, faster to start, serves responses faster, it has more "batteries included", etc, etc... What's the downside?