René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Silent errors in test.ts","articleBody":"I'm using angular-cli@1.0.0-beta.16, node@6.5.0 and karma@1.2.0 (on OS X El Capitan).\n\nWhen an exception is thrown while the spec files and their dependencies are loaded in [test.ts](https://github.com/angular/angular-cli/blob/master/packages/angular-cli/blueprints/ng2/files/__path__/test.ts#L32), the output `__karma__.error()` is barely helpful. In Chrome only 'ERROR' is printed to the node console and it's close to impossible to break on such a caught exception due to too many false positives. PhantomJS prints out a error stack but not the error message.\n\nIt would be great if you could log the error before re-throwing it.\n\nIn my case, @ngrx/effects@1.1.1 wasn't compatible with @angular@2.0.1, which was difficult to spot without sufficient error logging.\n","author":{"url":"https://github.com/renehamburger","@type":"Person","name":"renehamburger"},"datePublished":"2016-10-11T09:42:53.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/2640/angular-cli/issues/2640"}