-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Closed
Description
🐞 bug report
Is this a regression?
Yes, the application was working fine till 7.1.x
Description
I've relatively big hybrid app where angularjs is on a separate route. the app build broken after upgrade to angular 8
🔬 Minimal Reproduction
ng build --aot=true
🔥 Exception or Error
The below error happens for every html file in the angularjs part of the app.
ERROR in ./src/ng1/app/main/views/employee/endOfService/endOfService.html 1:0 Module parse failed: Unexpected token (1:0) You may need an appropriate loader to handle this file type. > ||ERROR in ./src/ng1/app/main/views/employee/contract/list/list.html 1:0 Module parse failed: Unexpected token (1:0) You may need an appropriate loader to handle this file type. > | |
🌍 Your Environment
Angular Version:
Angular CLI: 8.0.1
Node: 12.3.1
OS: win32 x64
Angular: 8.0.0
... animations, cdk, common, compiler, compiler-cli, core, forms
... language-service, material, material-moment-adapter
... platform-browser, platform-browser-dynamic, router, upgrade
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.800.1
@angular-devkit/build-angular 0.800.1
@angular-devkit/build-optimizer 0.800.1
@angular-devkit/build-webpack 0.800.1
@angular-devkit/core 8.0.1
@angular-devkit/schematics 8.0.1
@angular/cli 8.0.1
@angular/flex-layout 8.0.0-beta.26
@ngtools/webpack 8.0.1
@schematics/angular 8.0.1
@schematics/update 0.800.1
rxjs 6.5.2
typescript 3.4.5
webpack 4.30.0
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels