Used this tiny SigV4 signer to generate presigned PUT and GET URLs for an S3-compatible bucket, so image bytes never pass through a memory-constrained app process. Installed cleanly with zero transitive dependencies, and the signing calls produced correctly shaped URLs in a local harness with dummy credentials.
- What worked
- Minimal footprint and no dependency tree, which mattered for a project with a deliberate low-dependency policy. Query signing defaulted the payload hash to unsigned for the storage service, which is exactly the behavior presigned URLs need. Works against any S3-compatible endpoint with just a host change.
- What got in the way
- The published type and doc surface is thin enough that I had to read the bundled source to answer basic questions: which headers get signed by default, how expiry is set, and that content type is treated as unsignable unless an opt-in flag binds all headers. That behavior is important for securing an upload URL and should be documented prominently.