Angular generates chunks with no content on production build causes deployment issues related to MIME type

[tibin-carestack]

Which @angular/* package(s) are the source of the bug?

Don't known / other

Is this a regression?

Yes

Description

Angular 19 production builds (ng build --configuration production) are sometimes generating empty (0-byte) or malformed JavaScript chunk files (chunk-XXXXX.js). When deployed, browsers attempt to load these, resulting in "Failed to load module script: The server responded with a non-JavaScript MIME type" errors because the server serves an incorrect MIME type (e.g., text/html). This prevents the application from loading and causes significant deployment issues.

Impact: Application failure to load in production, broken user experience, difficult debugging due to misleading MIME type errors.

Expected Behavior: All production build chunks should contain valid JavaScript content and be served with text/javascript MIME type.

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)

Angular CLI: 19.2.13
Node: 20.18.0
Package Manager: npm 11.1.0
OS: win32 x64

Angular: 19.2.12
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1402.13
@angular-devkit/build-angular   19.2.13
@angular-devkit/core            19.2.13
@angular-devkit/schematics      19.2.13
@angular/cdk                    19.2.8
@angular/cli                    19.2.13
@schematics/angular             19.2.13
rxjs                            7.8.2
typescript                      5.8.2
zone.js                         0.15.0

Anything else?

No response

[alan-agius4]

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.

[clydin]

Content types are not controlled by the Angular application. Rather they are produced as response headers by the server and/or service hosting the application files.
Errors such as shown above typically indicate a misconfigured server and/or SPA fallback rule.

As mentioned in the previous comment, please provide a minimal reproduction demonstrating the output file issue.

[alan-agius4]

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.

[tibinthomas]

I fixed the issue by adding a dummy js code in all the chunk files which are empty. i was unable to pinpoint the exact issue.

but few clues that i have is this.

1. createComponrnt fn is used