Which @angular/* package(s) are the source of the bug?
compiler-cli, compiler
Is this a regression?
Yes
Description
After updating to Angular 13.1, CunkLoadError occurs when loading some modules.
It looks like the wrong js file was exported at build time.
css, looks wrong...
Below is the exported file name
src_app_authorized-routing-module_top-page-routing-module_top-page_module_ts.css, top-page-routing-module-top-page-module.js | top-page-routing-module-top-page-module
Below is the code for the applicable Routes
{
path: '',
loadChildren: () => import('./top-page-routing-module/top-page.module').then(m => m.TopPageModule)
},
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
ERROR Error: Uncaught (in promise): ChunkLoadError: Loading chunk src_app_authorized-routing-module_top-page-routing-module_top-page_module_ts failed.
(error: http://localhost:8091/src_app_authorized-routing-module_top-page-routing-module_top-page_module_ts.js)
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 13.1.1
Node: 14.17.6
Package Manager: npm 8.3.0
OS: win32 x64
Angular: 13.1.0
... animations, cdk, common, compiler, compiler-cli, core, forms
... material, platform-browser, platform-browser-dynamic, router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1301.1
@angular-devkit/build-angular 13.1.1
@angular-devkit/core 13.1.1
@angular-devkit/schematics 13.1.1
@angular/cli 13.1.1
@schematics/angular 13.1.1
rxjs 7.4.0
typescript 4.4.4
Anything else?
No response
Which @angular/* package(s) are the source of the bug?
compiler-cli, compiler
Is this a regression?
Yes
Description
After updating to Angular 13.1, CunkLoadError occurs when loading some modules.
It looks like the wrong js file was exported at build time.
css,looks wrong...Below is the exported file name
Below is the code for the applicable Routes
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version)Anything else?
No response