After running npm update my app will not build

ionic build produces the following error:

ERROR in AppComponent cannot be used as an entry component.
[ERROR] An error occurred while running subprocess ng.

When I ran npm update (prior to getting this error), the following was updated:

C:\Solutions\DTAS-ManifestManager>npm update
npm WARN deprecated @angular/http@7.2.16: Package no longer supported. Use @angular/common instead, see
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

core-js@2.6.11 postinstall C:\Solutions\DTAS-ManifestManager\node_modules\core-js
node -e “try{require(’./postinstall’)}catch(e){}”

npm WARN @capacitor/android@1.5.0 requires a peer of @capacitor/core@^1.5.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})

  • @angular/compiler-cli@7.2.16
  • @angular/language-service@7.2.16
  • @angular/core@7.2.16
  • @angular/compiler@7.2.16
  • @angular/router@7.2.16
  • @angular/platform-browser@7.2.16
  • @angular/forms@7.2.16
  • @angular/platform-browser-dynamic@7.2.16
  • @angular/http@7.2.16
  • @angular/common@7.2.16
  • @capacitor/android@1.5.0
  • @ionic-native/core@5.21.3
  • core-js@2.6.11
  • @ionic-native/screen-orientation@5.21.3
  • @types/jasminewd2@2.0.8
  • @ionic-native/status-bar@5.21.3
  • karma-coverage-istanbul-reporter@2.0.6
  • protractor@5.4.3
  • @ionic-native/splash-screen@5.21.3
  • rxjs@6.5.4
  • @ionic/angular@4.11.10
    added 23 packages from 9 contributors, removed 13 packages, updated 47 packages and audited 54283 packages in 173.088s

I have researched for a solution, but I found none so far. Other than the import statement on the SplashScreen class, nothing as changed in my app.module.ts. Here it is for reference. What could be causing this new problem from an npm update?

// Angular libraries
import { NgModule } from ‘@angular/core’;
import { BrowserModule } from ‘@angular/platform-browser’;
import { RouteReuseStrategy } from ‘@angular/router’;
import { HttpClientModule } from ‘@angular/common/http’;

// Ionic libraries
import { IonicModule, IonicRouteStrategy } from ‘@ionic/angular’;

// Other libraries
import { SplashScreen } from ‘@ionic-native/splash-screen’;
import { StatusBar } from ‘@ionic-native/status-bar/ngx’;
import { ScreenOrientation } from ‘@ionic-native/screen-orientation/ngx’;

// Manifest Manager classes and components
import { AppComponent } from ‘./app.component’;
import { AppRoutingModule } from ‘./app-routing.module’;

declarations: [AppComponent],
imports: [
providers: [
{ provide: RouteReuseStrategy, useClass: IonicRouteStrategy }
bootstrap: [AppComponent]

export class AppModule { }

I discovered the problem in my app.component.ts file. I had the following erroneous import statements:

import { Component } from ‘@angular/core/core’;
import { Router } from ‘@angular/router/router’;