Live data from Hacker News

Modern Node.js Patterns

kashw1n.com

21–30 of 448 posts

Re: Modern Node.js Patterns

#21

[flagged]

"Anyone who disagrees with me is a junior engineer." Just because a new feature can't always easily be slipped into old codebases doesn't make it a bad feature.

It’s pretty obviously bad. There was no need to design such a bad module system and basically destroy the work of others for no benefit.

Yes, it’s 100% junior, amateur mentality. I guess you like pointless toil and not getting things done.

Re: Modern Node.js Patterns

#22

[flagged]

isn’t this just like one of the few problems that is completely solvable today with LLM coding agents?

Ideally, a codemod would fix this, but the two module systems are incompatible for dynamic programming reasons.

Re: Modern Node.js Patterns

#23

Earlier quoted context omitted.

isn’t this just like one of the few problems that is completely solvable today with LLM coding agents?

Ideally, a codemod would fix this, but the two module systems are incompatible for dynamic programming reasons.

right, those transformations are a little too tricky for a codemod, but definitely still mechanical enough for LLMs to chug through is my guess.

Re: Modern Node.js Patterns

#27

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.

node fetch is WAY better than axios (easier to use/understand, simpler); didn't really know people were still using axios

Re: Modern Node.js Patterns

#28

Earlier quoted context omitted.

"Anyone who disagrees with me is a junior engineer." Just because a new feature can't always easily be slipped into old codebases doesn't make it a bad feature.

It’s pretty obviously bad. There was no need to design such a bad module system and basically destroy the work of others for no benefit. Yes, it’s 100% junior, amateur mentality. I guess you like pointless toil and not getting things done.

ESM is literally a standard. You can rant all you want, but you'll adopt it anyway.

Re: Modern Node.js Patterns

#29

Earlier quoted context omitted.

It’s pretty obviously bad. There was no need to design such a bad module system and basically destroy the work of others for no benefit. Yes, it’s 100% junior, amateur mentality. I guess you like pointless toil and not getting things done.

ESM is literally a standard. You can rant all you want, but you'll adopt it anyway.

Not really, from everything I can see, authors are basically forced to ship both, so it’s just another schism. Libraries that stopped shipping CJS we just never adopted, because we’re not dropping mature tech for pointless junior attitudes like this.

No idea why you think otherwise, I’m over here actually shipping.

Re: Modern Node.js Patterns

#30
post #27

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.

node fetch is WAY better than axios (easier to use/understand, simpler); didn't really know people were still using axios

I do miss the axios extensions tho, it was very easy to add rate-limits, throttling, retry strategies, cache, logging ..

You can obviously do that with fetch but it is more fragmented and more boilerplate

Post reply on HN