Tesseract.js doesn't work in CloudFlare Workers about tesseract.js

[Balearica]

I assume you are talking about CloudFlare Workers. CloudFlare Workers do not use Node.js--they use a custom runtime that uses V8, and implements a handful of Node.js APIs. Therefore, the fact that the CloudFlare worker is deciding to use the browser path is probably an intentional design decision on CloudFlare's part.

The Workers runtime also implements a subset of Node.js APIs as an optional, opt-in compatibility layer.
https://developers.cloudflare.com/workers/runtime-apis/

Regardless of the browser vs. Node.js issue, the code in question is attempting to spawn a worker, and I do not believe it is possible to spawn a worker within a CloudFlare worker. For context, the Tesseract.js createWorker function spawns a worker that executes Tesseract jobs on a separate thread. This uses web workers in browser, and the worker_threads module in Node.js. My understanding of CloudFlare workers are that they are inherently single-threaded, so do not support spawning more threads.

To use Tesseract.js within a single thread, the worker code would need to be executed directly. Making the worker scripts run standalone would likely not be that difficult--this would presumably just require using src/worker-script/index.js directly after deleting the exports.dispatchHandlers stuff that communicates with the main thread.

[penkzhou]

Thanks for your explanation. I will try your suggestion.