documentTextDetection is not a function
See original GitHub issueEnvironment details
- OS: Win 10
- Node.js version: 8.14.0
- npm version: 6.4.1
@google-cloud/vision
version: 1.2.0
Steps to reproduce
- just follow https://cloud.google.com/vision/docs/detecting-fulltext
- err when runs to the line
const [result] = await client.documentTextDetection(fileName);
I’m able to call .textDetection()
Thanks!
Issue Analytics
- State:
- Created 4 years ago
- Comments:23 (10 by maintainers)
Top Results From Across the Web
Err: documentTextDetection is not a function - Stack Overflow
documentTextDetection works for me node.js version 12.9.0 @google-cloud/vision version: 1.2.0 . Can you post the full code you run? – Brendan.
Read more >Dense document text detection tutorial | Cloud Vision API
If you are detecting text in scanned documents, try Document AI for optical character recognition, structured form parsing, and entity extraction.
Read more >StartDocumentTextDetection - Amazon Textract
StartDocumentTextDetection can analyze text in documents that are in JPEG, PNG, TIFF, and PDF format. The documents are stored in an Amazon S3...
Read more >Fix the OCR error Could Not Perform Recognition in Acrobat
Solution 1: Obtain a version of the document that does not contain renderable (editable) text. This message appears if the PDF document already ......
Read more >FIND function - Google Docs Editors Help
Returns the position at which a string is first found within text, case-sensitive. ... IFERROR : Returns the first argument if it is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@bcoe You are right. Original issue is resolved! Thank you all.
We should make sure the docs show the async wrapper as well.