syntax errors are printed to stderr, even when wrapped with try/catch

[sam-github]

I would expect no output to stderr when syntax or other exceptions are caught.

% node -e "try{require('/etc/passwd')}catch(e){}"

/etc/passwd:1
unction (exports, require, module, __filename, __dirname) { root:x:0:0:root:/r

Also, not that the missing f before "function" is not a cut-n-paste error, I'm not sure why that is happening, possibly because of binary in my passwd file.

[dougwilson]

This is how JavaScript works. You cannot catch a SyntaxError, as this is throw at the time the source is parsed. The try/catch only applies to runtime errors.

[sam-github]

a) the call to the require function happens at runtime, and b) the syntax error is caught, as you can see below:

% node -e 'try{require("/etc/passwd")}catch(e){console.log("<%s>",e)} console.log("caught it")'

/etc/passwd:1
unction (exports, require, module, __filename, __dirname) { root:x:0:0:root:/r
                                                                    ^
<SyntaxError: Unexpected token :>
caught it
%

You are probably thinking of examples like this:

try {
  some random text that is not js syntax
} catch(e) {
/// this will not be reached, nothing will, the code won't compile
}

But that's not what is happening.

[rlidwka]

Also, not that the missing f before "function" is not a cut-n-paste error, I'm not sure why that is happening

Just for the record: it's not a bug, pretty-printer just ate first "f" to fit the error in ~80 characters.

[domenic]

This is caused by #1310. Also relevant: #5848.

[indutny]

Should be fixed by #7049