3 ms·
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
by greener_grass 1y 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
- pier25 1y agoWould you rather use an officially maintained solution or some random package by a random author who might abandon the project (or worse)?
- greener_grass 1y agoThe S3 packages on NPM are maintained by AWS
- pier25 1y agoIndeed 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 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.
- greener_grass 1y agoSo let's put every package under the sun into the client? This approach does not scale. We should make NPM better.
- pier25 1y agoHow do you make NPM better? BTW I'm not saying we should kill NPM. What I'm saying is we should reduce our dependance on random packages. Bun doesn't need to add everything into the core engine. Eg: when using .NET you still add plenty of official Microsoft dependencies from Nuget.
- greener_grass 1y ago- NPM could migrate to reproducible builds of artefacts - Trust could be opt-in by default - Dependency installation could be made fully reproducible