Incorrect name in express-engine ng update schematic

[jonathonadams]

🐞 Bug report

What modules are related to this issue?

• aspnetcore-engine
• builders
• common
• express-engine
• hapi-engine
• module-map-ngfactory-loader

Is this a regression?

Unsure, I was not using @nguniversal/express-engine prior to v9

Description

After installing @nguniversal/express-engine with ng add @nguniversal/express-engine the wrong package name is shown if you run ng update.

The package name displayed is @nguniversal/aspnetcore-engine

🔬 Minimal Reproduction

Note: to demonstrate the update when running ng update, v9.0.0 is explicitly targeted.

$ npm i -g @angular/cli

$ ng new universal-app

$ ng add @nguniversal/express-engine@9.0.0

$ ng update

The output is:

    We analyzed your package.json, there are some packages to update:

      Name                               Version                  Command to update
     --------------------------------------------------------------------------------
      @nguniversal/aspnetcore-engine     9.0.0 -> 9.0.1           ng update @nguniversal/aspnetcore-engine

🌍 Your Environment

 9.0.4
Node: 12.9.1
OS: win32 x64

Angular: 9.0.4
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.900.4
@angular-devkit/build-angular     0.900.4
@angular-devkit/build-optimizer   0.900.4
@angular-devkit/build-webpack     0.900.4
@angular-devkit/core              9.0.4
@angular-devkit/schematics        9.0.4
@ngtools/webpack                  9.0.4
@nguniversal/builders             9.0.1
@nguniversal/common               9.0.0
@nguniversal/express-engine       9.0.0
@schematics/angular               9.0.4
@schematics/update                0.900.4
rxjs                              6.5.4
typescript                        3.7.5
webpack                           4.41.2

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}