If the error message includes the name of the file with the problem, try node <file.js>
If you have compile errors in code that is only compiled at runtime this trick will sometimes spot the problem and give you a line number. We've hit this in our nodeunit tests. Those wiser in the ways of V8 parsing and execution perhaps can explain why. -g On Sunday, January 24, 2016 at 11:48:08 PM UTC-8, Theodor Esenwein wrote: > > Hi there.... > > Can anyone help me to find a error. One of my NodeJS 5.5 / expressJS > application quits with the error: "syntax error unexpected end of file" > Unfortunately it gives no line at all. Any idea how to hunt and find the > location of this error? > > The hole project is in Typescript and compiles just fine... > > Any ideas? > > > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/12d1d1d0-b341-49f1-96ce-96ab843dca0f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
