Baptiste Manson bad3ec4720 fix #1239 - Command-line based syntax errors now print location ... Summary: Hi all! I took the path to implement a custom errorHandler, to be more aligned with the rest of the code, but it may be a mistake. I reached that point. ```bash echo "(){}" | yarn prepack yarn prepack v0.27.5 $ node lib/prepack-cli.js Unexpected token (1:1) found in stdin Error: A fatal error occurred while prepacking. + (full stack trace) error Command failed with exit code 1. ``` and when srcmapIn is given but not existing: ```bash echo "(){}" | yarn prepack -- --srcmapIn notExisting yarn prepack v0.27.5 $ node lib/prepack-cli.js "--srcmapIn" "notExisting" No sourcemap found at notExisting. Unexpected token (1:1) found in stdin + (stack trace) ``` Finally when using files with syntax error: ```bash yarn prepack ../notepad/test.js yarn prepack v0.27.5 $ node lib/prepack-cli.js "../notepad/test.js" Unexpected token (1:3) found in input file ../notepad/test.js + (stack trace) ``` Closes https://github.com/facebook/prepack/pull/1272 Differential Revision: D6595324 Pulled By: hermanventer fbshipit-source-id: 6f73a15db5710585ffc9579f4487217a98f921f5		2017-12-18 13:56:26 -08:00
..
StdIn.js	fix #1239 - Command-line based syntax errors now print location	2017-12-18 13:56:26 -08:00