Modern Node.js Patterns

Post by DimmieMan » Mon, Aug 04, 2025, 5:40 AM UTC

jiggawatts wrote: post #175

drewbitt wrote: post #169

Earlier quoted context omitted.

Compile speed and a subjective DX opinion are very debatable. The breadth of npm packages is a good reason to use node. It has basically everything.

It has terrible half-completed versions of everything, all of which are subtly incompatible with everything else. I regularly see popular packages that are developed by essentially one person, or a tiny volunteer team that has priorities other than things working . Something else I noticed is that NPM packages have little to no "foresight" or planning ahead... because they're simply an itch that someone needed to scr…

Post by motorest » Mon, Aug 04, 2025, 6:01 AM UTC

tankenmate wrote: post #221

simonw wrote: post #113

Whoa, I didn't know about this: # Run with restricted file system access node --experimental-permission \ --allow-fs-read=./data --allow-fs-write=./logs app.js # Network restrictions node --experimental-permission \ --allow-net=api.example.com app.js Looks like they were inspired by Deno. That's an excellent feature. https://docs.deno.com/runtime/fundamentals/security/#permiss...

I wouldn't trust it to be done right. It's like a bank trusting that all their customers will do the right thing. If you want MAC (as opposed to DAC), do it in the kernel like it's supposed to be; use apparmor or selinux. And both of those methods will allow you to control way more than just which files you can read / write.

Post by seniorsassycat » Mon, Aug 04, 2025, 6:17 AM UTC

serguzest wrote: post #40

One thing you should add to section 10 is encouraging people to pass `cause` option while throwing new Error instances. For example new Error("something bad happened", {cause:innerException})

Post by int_19h » Mon, Aug 04, 2025, 6:18 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 pjmlp » Mon, Aug 04, 2025, 6:19 AM UTC

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.