Comment by greener_grass
Comment by greener_grass 6 days ago
Can someone explain the advantage of this?
If I want S3 access, I can just use NPM
If I don't want S3 access, I don't want it integrated into my runtime
Comment by greener_grass 6 days ago
Can someone explain the advantage of this?
If I want S3 access, I can just use NPM
If I don't want S3 access, I don't want it integrated into my runtime
Indeed but I was arguing about a general point.
I'd be surprised if any of your Node projects had less than 100 total deps of which a large number will be maintained by a single person.
See Express for example. 66 total deps with 26 deps relying on a single maintainer.
https://npmgraph.js.org/?q=express
But even in the case of the official aws-sdk they recently deprecated v2. I now need to update all my not-so-old Node projects to work with the newer version. Probably wouldn't have happened if I had used Bun's S3 client.
So let's put every package under the sun into the client?
This approach does not scale. We should make NPM better.
Would you rather use an officially maintained solution or some random package by a random author who might abandon the project (or worse)?