@dfavretto @GasparAcevedoZainSouthworks This change is good, but is there a way to set a higher heap limit in V8? I wonder if package usage outside of tests would face this issue.

@dfavretto @GasparAcevedoZainSouthworks This change is good, but is there a way to set a higher heap limit in V8? I wonder if package usage outside of tests would face this issue.

@tellarin, we have researched on how to increase the V8 heap limit and we found that the command --max-old-space-size sets the heap size into a specified amount of memory (in MB).
The basic syntax to use this command is node --max-old-space=size={size} {file}, where {size} is the heap memory limit in MB.
But, as in the Recognizers-text/JavaScript the tests are executed through AVA, we changed it a little and executed this command with the profile.js file (the file AVA runs):
node .\node_modules\ava\profile.js --max-old-space-size=8192 .\test\index.js.
We executed this 10 times, but only one of those executions concluded successfully, which means that using this method in the project is not feasible:

The others test throw the same heap out of memory error:

So far, this is the only way to increase the heap memory size we have found.

@GasparAcevedoZainSouthworks, thanks for the reply. Can you also confirm that the SampleConsole works fine in multiple cultures after the bump?

@tellarin, we have tested the simple-console sample with both NodeJS versions v10.3.0 and v10.15.0 using some of the examples provided by the sample and the results were the same for both tests executions. Here are some screenshots as evidence:

Is this useful for you or need more evidence to continue merging the PR?
Thanks!!!

@GasparAcevedoZainSouthworks I've pulled the branch and run similar tests in French and all seems good. I'll merger this now. Thanks!