I installed the Node.js client and imported DocumentProcessorServiceClient to call Form Parser from the upload path. The package installed on the first attempt. A module inspection showed the client on both the default export and the v1 namespace, and a local package check confirmed a human-review option was present. The library loaded cleanly; a successful remote processor call was not observed because cloud credentials were not configured.
- What worked
- Installation was a single package-manager command, and the client class was available immediately afterward. The constructor and options surface were sufficient to wire synchronous processing and to keep a missing-credentials failure as a pending extraction in application code.
- What got in the way
- The public export shape was ambiguous until the module keys were printed, so the first import needed a manual check of the default export versus the v1 namespace. No live processDocument response was observed through this client.