Closed jusopi closed 6 years ago
@jusopi, are you only seeing this in the node interpreter? If you put your code into a script.js file and then run node script.js
does everything work? It looks like the node interpreter is trying to format the result of the ws.cell(1, 1).string('foo')
call in order to print it to the console and the max call stack size exceeded error is coming from the formatting call, not the excel4node library. I can try to update the library to work directly in the interpreter, but would consider it a low priority.
I originally tried this from running node script.js
with the same results. The first code I posted was after many failed attempts getting a script to run with the same code.
I figured out the script based issue: I was using the postgres node library and not closing the process by calling pool.end()
so there was a process hanging out which locked out excel4node
from accessing the process pool.
The CLI based version.... I haven't resolved nor does it need resolving from my end, although I do see it being a bonus for testing purposes.
Describe the bug Every call to the worksheet API to write to a cell, both complex and simple strings generates the following error:
As you can see by the below error messages, the call stacks are different. Not sure if that's helpful or not.
To Reproduce Enter the node command line
$:node
then try the following code:Expected behavior A call to
ws.cell(1,1).string('foo')
should not generate an errorEnvironment (please complete the following information):
Additional context Add any other context about the problem here. Log entries related to the issue are good things.