[deleted]
Modern Node.js Patterns
11–20 of 448 posts
Re: Modern Node.js Patterns
#12[flagged]
Re: Modern Node.js Patterns
#13Don’t forget the native typescript transpiler which reduces the complexity a lot for those using TS
Re: Modern Node.js Patterns
#14Earlier quoted context omitted.
One of the core things Node.js got right was streams. (Anyone remember substack’s presentation “Thinking in streams”?) It’s good to see them continue to push that forward.
Why? Why is a stream better than an array? Why is the concept of a realtime loop and for looping through a buffer not sufficient?
I think there are several reasons. First, the abstraction of a stream of data is useful when a program does more than process a single realtime loop. For example, adding a timeout to a stream of data, switching from one stream processor to another, splitting a stream into two streams or joining two streams into one, and generally all of the patterns that one finds in the Observable pattern, in unix pipes, and more generally event based systems, are modelled better in push and pull based streams than they are in a real time tight loop. Second, for the same reason that looping through an array using map or forEach methods is often favored over a for loop and for loops are often favored over while loops and while loops are favored over goto statements. Which is that it reduces the amount of human managed control flow bookkeeping, which is precisely where humans tend to introduce logic errors. And lastly, because it almost always takes less human effort to write and maintain stream processing code than it does to write and maintain a real time loop against a buffer.
Hopefully this helps! :D
Re: Modern Node.js Patterns
#15Earlier quoted context omitted.
One of the core things Node.js got right was streams. (Anyone remember substack’s presentation “Thinking in streams”?) It’s good to see them continue to push that forward.
Why? Why is a stream better than an array? Why is the concept of a realtime loop and for looping through a buffer not sufficient?
A stream is not necessarily always better than an array, of course it depends on the situation. They are different things. But if you find yourself with a flow of data that you don't want to buffer entirely in memory before you process it and send it elsewhere, a stream-like abstraction can be very helpful.
Re: Modern Node.js Patterns
#16The 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.
Re: Modern Node.js Patterns
#17Node now has limited supports for Typescript and has SQLite built in, so it becomes really good for small/personal web oriented projects.
Re: Modern Node.js Patterns
#18Earlier quoted context omitted.
Architecture astronaut is a term I hadn't heard but can appreciate. However I fail to see that here. It's a fair overview of newish Node features... Haven't touched Node in a few years so kinda useful.
It's a good one with some history and growing public knowledge now. I'd encourage a deep dive, it goes all the way back to at least CPP and small talk. While I can see some arguments for "we need good tools like Node so that we can more easily write actual applications that solve actual business problems", this seems to me to be the opposite. All I should ever have to do to import a bunch of functions from a file is…
Isn't that exactly the syntax being recommended? Could you explain what exactly in the article is a solution in search of a problem?
Re: Modern Node.js Patterns
#19[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.
Re: Modern Node.js Patterns
#20[flagged]
isn’t this just like one of the few problems that is completely solvable today with LLM coding agents?