Please complete the first part of the issue template asking what version of Tesseract.js you are using.

Additionally, please post the error message (if any) that occurs when you leave workerPath as the default value.

The NetworkError error appears to be fairly literal--indicating that the workerPath argument is not pointing to a valid worker.min.js file. Presumably http://localhost:57232/node_modules/tesseract.js/dist/worker.min.js does not exist on your local site. Therefore, I would expect the solution would be editing your workerPath or Cypress configuration.

I have personally used Cypress with the latest version of Tesseract.js for another project, so am disinclined to believe that Tesseract.js is incompatible with Cypress.

I am using latest version teseracct.js v5.0.3, below is the error while I am using default configuration.
btw, I can access http://localhost:57232/node_modules/tesseract.js/dist/worker.min.js in browser. so I believe the file is exist on local.

(uncaught exception)Error: Uncaught NetworkError: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https://cdn.jsdelivr.net/npm/tesseract.js@v5.0.3/dist/worker.min.js' failed to load.
(uncaught exception)TypeError: Cannot create property 'isPending' on string 'Uncaught NetworkError: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https://cdn.jsdelivr.net/npm/tesseract.js@v5.0.3/dist/worker.min.js' failed to load.'

I do not know why importScripts would throw network errors when provided a valid path. You can try setting workerBlobURL: false in the createWorker options. This bypasses the importScripts statement that loads the worker.min.js file, however importScripts is still used to download Tesseract.js-core, so that may simply lead to a different error message being thrown.

If the issue persists and you want me to look further, I would need to be provided a reproducible example repo that I can clone and run. As noted above, I am able to use Cypress with the latest version of Tesseract.js on my system and it works as expected.

Also, you should delete the worker.reinitialize statement. createWorker returns a worker that is already initialized in the language that you specify. The function worker.reinitialize re-initializes the worker with a new language/OEM--it only needs to be run if you want to switch from English to Chinese (for example) with an existing worker.

thanks for responding, after I change setting workerBlobURL: false, the address changed to an invalid address below.
'http://localhost:59744/__cypress/node_modules/tesseract.js-core/tesseract-core-simd-lstm.wasm.js' failed to load.
I try to use a absolute path, the scripts failed with following error.
Failed to construct 'Worker': Access to the script at 'file:///C:/Users/tdeng/Documents/tesseractjs/node_modules/tesseract.js/dist/worker.min.js' is denied by the document's Content Security Policy.

Browsers are categorically disallowed from accessing files on your local file system--any path starting with file:// will not work in a browser for security reasons. Additionally, you generally don't want to be using paths relative to the current file (i.e. paths starting with ./ or ../) for langPath or workerPath as these will be broken if the script is run out of a different directory (which is presumably what Cypress is doing).

Instead, if you want to always access the node_modules directory regardless of where the script is being run, you would do /node_modules/tesseract.js-core, which will always resolve to [domain]/node_modules/tesseract.js-core.

have tried according to above suggestions, I am not able to make script working in Cypress environment, so we can get the conclusion that Tesseract.js is incompatible with Cypress, right? if so, do you have plan to make tesseract.js officially support Cypress testing, which I think it will do great help to visualization testing. thanks!

especially, if there are canvas components, to verify message in canvas, tesseract.js should make a big difference.

As I stated above, Tesseract.js can be used with Cypress. I personally use Cypress with a project that uses the latest version of Tesseract.js.

It sounds like there is something wrong with your testing environment, your Cypress configuration, or the specific version of Cypress you are using is bugged. The error you report above is that importScripts([path]) is failing, despite path being valid. This cannot be a bug with Tesseract.js.

If you create a repo with a minimal reproducible with Cypress + Tesseract.js, then I can clone and look into this further. However, without something I can clone and run, there is nothing further I can do to help with this.

I zipped my project, and the issue could be reproduced, hope this can help to figure out the problem.
Uploading tesseractjsdebug.zip…

seems like the zipped file has problem, I have upload my cypress code to following github location, could you pls have a look? thanks!
https://github.com/dpmylove/ShareForDebugTesseractJS

find info for the error: Refused to load the script 'http://localhost:63292/node_modules/tesseract.js/dist/worker.min.js' because it violates the following Content Security Policy directive: "script-src 'unsafe-eval'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. so how to avoid this restriction?

I looked at your repo, and it does not look like you have a website for Cypress to test. Rather, it looks like you're trying to run recognition within the .cy.js files defining the test specifications. This will not work, and would not be desirable to do even if it did work, as it would mean that no separate application is being tested.

Cypress should be used to test a website. The JavaScript code that contains the Cypress tests should only contain the testing code. It should not attempt to run application code (in this case, recognition).

Separate from the testing code, you should have a website that recognizes an image using Tesseract.js. The examples in this repo can be used for a basic example. Then, you can write a Cypress script that interacts with the website to run recognition.

I actually run this to test a web and encounter problems, in order to make it simple, so I create this repo. This error happens while in tesseract initial state. So I think not test web is not the reason. anyway, I will update this repo to test web later.

Closing this issue as I believe Tesseract.js does work with Cypress and any issues are due to a particular project configuration. We can reopen if a reproducible example repo of Cypress failing to work with the basic example code is provided.