CLI: Add try/catch on readFileAsJson to improve error message

[andrefarzat]

Issue:
When running npx sb init in an angular project, one json file was wrong (with a trailing comma) and it took me too much time to figure out which json file was wrong.

What I did

Added try/catch wrapping the JSON.parse to improve error message and the user be aware which json file is wrong

How to test

My test case is having a tsconfig.app.json with a wrong json in the file. In an angular project, the command npx sb init reads about 3 json files ( among angular.json, tsconfig.json and tsconfig.app.json )

[phated]

I think this is a good idea! I just don't want to lose the stack trace, instead we should add additional information somehow. 🤔

[phated]

Maybe we should log the filename and still throw the original error? I would hate to lose the stack trace for debugging

[andrefarzat]

Changed as you suggested. Just added chalk.red on it:

try {
    return JSON.parse(jsonContent);
  } catch(e) {
    console.error(chalk.red('Invalid json on file: ' + filePath));
    throw e;
}

[shilman]

Yay. Thanks @andrefarzat !!!