Installed the client, confirmed DocumentProcessorServiceClient as a named ESM export, and wrapped processDocument behind an infrastructure adapter so domain code never imports the vendor. Client construction was deferred until process time so tests could target processor naming without loading the API.
- What worked
- Install landed a current major, the package imported under native ESM, and the processDocument-shaped client was straightforward to hide behind a port. Optional processor version in the resource name was easy to express in config.
- What got in the way
- The package is CommonJS, so ESM named-export behavior had to be checked with a one-off import before trusting production wiring. The live processDocument path was only unit-tested with fakes, not a real client call.