René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Provide better story for individual migration results","articleBody":"This issue impacts 9.0.0-rc.0 and happened while updating https://github.com/johannesjo/super-productivity and https://github.com/SAP/cloud-commerce-spartacus-storefront.\r\n\r\nA failed update will show a message saying both the individual migration and the update failed:\r\n```\r\n× Package install failed, see above.\r\nThe update failed. See above.\r\ngit HEAD was at 85f08a4d93e684566f751e38e2a2feffe0194cd9 before migrations.\r\n×  Migration failed. See above for further details.\r\n```\r\n\r\nThe update below did not finish successfully however, and instead just shows the last migration as successful (@devversion confirms this). In this case the migration shows an error that it seems to suggest was actually recovered from, but it fact the intent is that the migration was interrupted and should later be resumed.\r\n```\r\n\u003e  Undecorated classes with DI migration.\r\n   As of Angular 9, it is no longer supported to use Angular DI on a class that does not have an Angular decorator.\r\n   Read more about this here: https://v9.angular.io/guide/migration-undecorated-classes\r\n    \r\n    This migration uses the Angular compiler internally and therefore projects that no longer build successfully after the update cannot run the migration. Please ensure there are \r\nno AOT compilation errors and rerun the migration.. The following project failed: projects/storefrontlib/tsconfig.lib.json\r\n    \r\n    TypeError: Cannot read property 'module' of undefined\r\n    \r\n    Could not migrate all undecorated classes that use dependency\r\n    injection. Some project targets could not be analyzed due to\r\n    TypeScript program failures.\r\n\r\n    Migration can be rerun with: \"ng update @angular/core --from 8.0.0 --to 9.0.0 --migrate-only\"\r\n\r\n√  Migration succeeded.\r\n```\r\n\r\nA completely successful migration will look the same as the migration above though:\r\n```\r\nkamik@RED-X1C6 MINGW64 /d/sandbox/latest-app (master)\r\n$ ng update @angular/cli @angular/core --next\r\nThe installed Angular CLI version is older than the latest published version.\r\nInstalling a temporary version to perform the update.\r\nInstalling packages for tooling via yarn.\r\nwarning @angular-devkit/architect@0.900.0-rc.0: The engine \"pnpm\" appears to be invalid.\r\nwarning @schematics/angular@9.0.0-rc.0: The engine \"pnpm\" appears to be invalid.\r\nwarning @angular-devkit/schematics@9.0.0-rc.0: The engine \"pnpm\" appears to be invalid.\r\nwarning @angular-devkit/core@9.0.0-rc.0: The engine \"pnpm\" appears to be invalid.\r\nwarning @schematics/update@0.900.0-rc.0: The engine \"pnpm\" appears to be invalid.\r\nwarning @angular/cli@9.0.0-rc.0: The engine \"pnpm\" appears to be invalid.\r\nInstalled packages for tooling via yarn.\r\nUsing package manager: 'yarn'\r\nCollecting installed dependencies...\r\nFound 35 dependencies.\r\nFetching dependency metadata from registry...\r\n    Updating package.json with dependency @angular/cli @ \"9.0.0-rc.0\" (was \"8.3.17\")...\r\n    Updating package.json with dependency @angular/core @ \"9.0.0-rc.0\" (was \"8.2.13\")...\r\n    Updating package.json with dependency @angular/language-service @ \"9.0.0-rc.0\" (was \"8.2.13\")...\r\n    Updating package.json with dependency @angular/compiler-cli @ \"9.0.0-rc.0\" (was \"8.2.13\")...\r\n    Updating package.json with dependency @angular/animations @ \"9.0.0-rc.0\" (was \"8.2.13\")...\r\n    Updating package.json with dependency @angular/platform-browser @ \"9.0.0-rc.0\" (was \"8.2.13\")...\r\n    Updating package.json with dependency @angular/platform-browser-dynamic @ \"9.0.0-rc.0\" (was \"8.2.13\")...\r\n    Updating package.json with dependency @angular/common @ \"9.0.0-rc.0\" (was \"8.2.13\")...\r\n    Updating package.json with dependency @angular/compiler @ \"9.0.0-rc.0\" (was \"8.2.13\")...\r\n    Updating package.json with dependency @angular/forms @ \"9.0.0-rc.0\" (was \"8.2.13\")...\r\n    Updating package.json with dependency @angular/router @ \"9.0.0-rc.0\" (was \"8.2.13\")...\r\n    Updating package.json with dependency @angular-devkit/build-angular @ \"0.900.0-rc.0\" (was \"0.803.17\")...\r\nUPDATE package.json (1636 bytes)\r\n√ Packages installed successfully.\r\n** Executing migrations of package '@angular/cli' **\r\n\r\n\u003e  Update an Angular CLI project to version 9.\r\nUPDATE angular.json (6359 bytes)\r\nUPDATE package.json (1637 bytes)\r\nUPDATE server.ts (1863 bytes)\r\n√ Packages installed successfully.\r\n√  Migration succeeded.\r\n\r\n\u003e  Update lazy loading syntax to use dynamic imports.\r\n√  Migration succeeded.\r\n\r\n** Executing migrations of package '@angular/core' **\r\n\r\n\u003e  Static flag migration.\r\n   Removes the `static` flag from dynamic queries.\r\n   As of Angular 9, the \"static\" flag defaults to false and is no longer required for your view and content queries.\r\n   Read more about this here: https://v9.angular.io/guide/migration-dynamic-flag\r\n√  Migration succeeded.\r\n\r\n\u003e  Missing @Injectable migration.\r\n   In Angular 9, enforcement of @Injectable decorators for DI is a bit stricter.\r\n   Read more about this here: https://v9.angular.io/guide/migration-injectable\r\n√  Migration succeeded.\r\n\r\n\u003e  ModuleWithProviders migration.\r\n   In Angular 9, the ModuleWithProviders type without a generic has been deprecated.\r\n   This migration adds the generic where it is missing.\r\n   Read more about this here: https://v9.angular.io/guide/migration-module-with-providers\r\n√  Migration succeeded.\r\n\r\n\u003e  NGCC postinstall migration.\r\n   Adds an ngcc invocation to npm/yarn's postinstall script.\r\n   Read more about this here: https://v9.angular.io/guide/migration-ngcc\r\nUPDATE package.json (1743 bytes)\r\n√ Packages installed successfully.\r\n√  Migration succeeded.\r\n\r\n\u003e  Renderer to Renderer2 migration.\r\n   As of Angular 9, the Renderer class is no longer available.\r\n   Renderer2 should be used instead.\r\n   Read more about this here: https://v9.angular.io/guide/migration-renderer\r\n√  Migration succeeded.\r\n\r\n\u003e  Undecorated classes with decorated fields migration.\r\n   As of Angular 9, it is no longer supported to have Angular field decorators on a class that does not have an Angular decorator.\r\n   Read more about this here: https://v9.angular.io/guide/migration-undecorated-classes\r\n√  Migration succeeded.\r\n\r\n\u003e  Undecorated classes with DI migration.\r\n   As of Angular 9, it is no longer supported to use Angular DI on a class that does not have an Angular decorator.\r\n   Read more about this here: https://v9.angular.io/guide/migration-undecorated-classes\r\n√  Migration succeeded.\r\n```\r\n\r\nWe should confirm the update finished, was successful, or if it was interrupted midway and should later be continued.","author":{"url":"https://github.com/filipesilva","@type":"Person","name":"filipesilva"},"datePublished":"2019-11-01T20:44:08.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":12},"url":"https://github.com/16016/angular-cli/issues/16016"}