angular / angular-cli

CLI tool for Angular
https://cli.angular.io
MIT License
26.77k stars 11.97k forks source link

ChunkLoadError After Upgrading to Angular Version 13.3.9 #23834

Closed jatinkumar159 closed 2 years ago

jatinkumar159 commented 2 years ago

🐞 Bug report

Is this a regression?

Yes ### Description After updating to Angular 13.3.9 from Angular 11, ChunkLoadError occurs when loading some modules. Error comes in node_modules_stompjs_index_js and custom module. ## πŸ”¬ Minimal Reproduction No ## πŸ”₯ Please provide the exception or error you saw Error: Uncaught (in promise): ChunkLoadError: Loading chunk node_modules_stompjs_index_js failed. (error: http://localhost:4500/ng/node_modules_stompjs_index_js.js) ChunkLoadError: Loading chunk node_modules_stompjs_index_js failed. ## 🌍 Your Environment
Angular CLI: 13.3.9
Node: 16.13.1
Package Manager: npm 8.1.2
OS: darwin arm64
Angular: 13.3.11
... animations, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router
Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1401.3
@angular-devkit/build-angular   13.3.9
@angular-devkit/core            13.3.9
@angular-devkit/schematics      13.3.9
@angular/cdk                    13.3.9
@angular/cli                    13.3.9
@schematics/angular             13.3.9
rxjs                            6.6.7
typescript                      4.6.4
**Anything else relevant?** I am using Macbook Pro M1 chip
alan-agius4 commented 2 years ago

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?

You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

jatinkumar159 commented 2 years ago

Hi @alan-agius4 ,

Setting-up a minimal repo won't be possible. If required I can share with you the package.json and package-lock.json file with you.

alan-agius4 commented 2 years ago

I am afraid that without a minimal reproduction we cannot action this issue. The package.json and package-lock.json alone will not be enough to reproduce the problem.

alan-agius4 commented 2 years ago

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.

If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.

angular-automatic-lock-bot[bot] commented 2 years ago

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.