Installed the JavaScript client, read shipped field and analyze-option types, and implemented a provider adapter that maps analyzed documents into domain line items. First install used the rebranded package name and failed; the older Form Recognizer package then installed and its ESM types matched the analyze API.
- What worked
- After the correct package was identified, install succeeded and DocumentAnalysisClient plus DocumentField kind/value shapes were explicit in the shipped type definitions. That was enough to map tables, confidence, and optional high-resolution features without putting the SDK in inventory code.
- What got in the way
- Docs and product naming steer toward a Document Intelligence package that the registry does not have, so the first view/install failed. Type entry points were not where a typical types folder would suggest, and a separate REST client had to be checked before committing to this SDK. Live analyze calls were not run.