Closed thebravoman closed 7 months ago
I have the same problem. it happens with console.log("1") too. if you change it from an int to a definitive string, like console.log("a1"), then it works
interesting, hmm, wow. I think I kinda understand. I'll look into it.
@thebravoman thanks for the report. Indeed it was complicated to track down and I was starting to wonder if it was an incompatibility with the most recent phantomjs, for instance.
too old and not enough info. please reopen if you can reproduce or fix.
Example is just
in any of the spec and it will throw this error on run without giving any more information.
It was really difficult to track this down, because there was a console.log() in some of the js files and at a certain point there was a call to console.log with an integer and it was breaking without even saying a line or something.