From 6ceb9034dc99e5e9f791c988eda2cc9ce99bc2e1 Mon Sep 17 00:00:00 2001
From: Paul Gschwendtner <paulgschwendtner@gmail.com>
Date: Tue, 14 May 2019 19:59:26 +0200
Subject: [PATCH] fix(core): static-query migration errors not printed properly
 (#30458)

Apparently the devkit logger is not able to properly print
out error objects, so we need to convert them to a string
before in order to make the error visible to the user.

This is not testable without an e2e test that validates the CLI
terminal output.

PR Close #30458
---
 packages/core/schematics/migrations/static-queries/index.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/core/schematics/migrations/static-queries/index.ts b/packages/core/schematics/migrations/static-queries/index.ts
index 089d369d7c..efc8a5f525 100644
--- a/packages/core/schematics/migrations/static-queries/index.ts
+++ b/packages/core/schematics/migrations/static-queries/index.ts
@@ -192,7 +192,7 @@ async function runStaticQueryMigration(
           `the update cannot use the template migration strategy. Please ensure ` +
           `there are no AOT compilation errors.`);
     }
-    logger.error(e);
+    logger.error(e.toString());
     logger.info(
         'Migration can be rerun with: "ng update @angular/core --from 7 --to 8 --migrate-only"');
     return [];