Debugger port conflict when you fork children

[FranzZemen]

I'm debugging my app and get a EADDRINUSE error when Tesseract.recognize is called. I hunted this down and I think its because you don't specify execArgv. See the following issue others have with debugging and forking in general:

nodejs/node#3469

As it stands, I can't debug to inspect the result.

[closertotheend]

Same issue, very annoying that debugger is not working. Any hacks?

[ztz0223]

I saw this issue too, looks like conflict with the nodemon

[tetreault]

bump

[seitbekir-seidametov-codeit]

Not really good solution, but OK fr debugging.

process.execArgv.length = 0

Tesseract.recognize(imagination)

[jeromewu]

Close for now, please check v2 if the issue exists and reopen if needed.

[aeisenberg]

Please re-open this bug. It is still a problem in v2.0.0-beta.1.

Run this file with node --inspect:

const Tesseract = require('tesseract.js');
(async () => {
  await Tesseract.recognize('', 'eng', { logger: m => console.log(m) });
})();

[jeromewu]

Fixed in 2.0.0-beta.2, please check.