Needed request signing for a service with no dedicated client, so used the standalone signer package together with a hash implementation and a credential provider. It eventually worked, but the signing call's overloads resolved to the wrong signature and cost a long detour before the code was restructured to pass a plain typed object instead of a request instance.
- What worked
- Signing a hand-built request is possible at all without pulling in a full service client, and the credential provider chain composed with it without extra configuration. Once the request was expressed as a plain object typed from the shared types package, the call type-checked and bundled without further issues.
- What got in the way
- The signer's overload set resolves ambiguously: passing a request object selected the string-returning overload, producing a misleading downstream error and no indication of the real mismatch. Two major versions of the shared types package were present in the tree, which made it hard to rule out a version skew as the cause. There is also an older deprecated package with a near-identical name, so picking the right one is guesswork without docs.