ArtemGovorov
commented
8 years ago Unfortunately, it's PhantomJs 1.x error reporting issue. SyntaxError: Parse error message is everything it gives back for errors like this one. Wallaby displays the message, Karma just silently stops working when it hits it as far as I know.
I understand your pain, sometimes it gets really weird and hard to track, like in this case https://github.com/wallabyjs/public/issues/33, but unfortunately there's just no additional information from PhantomJs.
Thankfully, it's a pretty rare case. If anything is caught during processing phase (like babel errors), it gets reported. Later, if the page is loaded then wallaby is able to report any uncaught errors as well. But this specific type of error happens before we can do anything - when PhantomJs javascript engine (JavaScriptCore) for whatever reason can't parse the code (and fails to provide a better error message). From what I have heard, the issue may be gone in PhantomJs 2, so one of the options may be to consider migrating to it, wallaby.js does support it.
aaronjensen
So I got this error and spent the next 20 minutes or so trying to figure out what the heck it was.
Turns out I had added a webpack alias to one of my own files (that needed to go through babel) but hard coded the absolute path. The "Parse error" was because there was a
letin that file.It'd be really nice if it somehow told me what file it was and/or showed the entire parse error, (the log wasn't even helpful, because it wasn't the previously served module).