left-pad VS readable-stream

It's pretty easy to find that the example I gave isn't gamed... A cursory search on GitHub can find a couple examples like dotenv [1] and npm's cli [2] both use it via an older version of nodejs/readable-stream [3].

There's also the classic left-pad debacle - https://github.com/left-pad/left-pad/issues/4

[1] - https://github.com/motdotla/dotenv/blob/master/package-lock....

when using some other modern libraries like tailwind, you have to update the Next.js version carefully or you may have some errors following the Next.js update. Nothing new in javascript world, if something is working it's not guaranteed it will last :) It is important to really read the Next.js release notes as the base configuration may change in between the releases.

It's OK, it's reddit, it happens. I will say however that unless you are deploying to a windows server on premise somewhere you are using open source. (And soon even that won't be true because eventually Windows is going to be based on Linux.) I'm not asking people to give up their weekends or anything, but IMO if you consume open source, you have an obligation to contribute back something. Even if it's just reporting a bug on some library that you use.

Funny story, on the day that they unpublished it, the package.json states the license to be "WTFPL", which allows NPM to Do What The Fuck You Want To

It had been optimized (and deprecated) since then. See https://github.com/left-pad/left-pad/blob/master/index.js

If it's a readable stream, you can just directly consume it with an async iterator: https://nodejs.org/api/stream.html#streams-compatibility-wit...

Node.js Stream

Note that the older Node.js streams API hasn't been deprecated or removed. It will co-exist with the new API, and it even provides a way to convert from a web stream and vice versa using the .fromWeb() and .toWeb() methods (both added in Node 17, although both methods still retain their experimental status).

Nodejs has piepes with its stream https://nodejs.org/api/stream.html

You then want what's invoked by that event to be consumed as a Response. NodeJS has something to replicate this with stream consumers where you can do all the response.text() you normally do.

[3] - https://github.com/nodejs/readable-stream/

First, we create a NodeJS ReadStream using fs.createWriteStream to open the test.log file in "append" mode. Then we start recursively looping using setTimeout. This simulates an application that logs text in the file at a variable rate. At each iteration:

This needs a comparison with streams, which is the standard way to achieve this in Node.js land.

https://nodejs.org/api/stream.html