Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflicting build chunk size #15267

Closed
KishoreBarik opened this issue Aug 7, 2019 · 5 comments
Closed

Conflicting build chunk size #15267

KishoreBarik opened this issue Aug 7, 2019 · 5 comments
Labels
area: @angular-devkit/build-angular devkit/build-angular:browser freq1: low Only reported by a handful of users who observe it rarely needs: investigation Requires some digging to determine if action is needed severity1: confusing type: bug/fix
Milestone

Comments

@KishoreBarik
Copy link

🐞 Bug report

Command (mark with an x)

- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Facing issue with main.js bundle chunk size. Particularly rxjs. (Relates to #9069 )

image

Environment:

image

Note
Earlier I was seeing the left panel (900+ KB) was occupied by polyfills(at that time Size of Rx was nearly 53KB). So to solve this I found out I had to mention "es5BrowserSupport": true in angular.json and commented all imports in polyfills.ts except import "zone.js/dist/zone";.
Now I am seeing similar amount of size is being taken by RxJs. If I uncomment the polyfill imports the RxJs is back to around 53 KB but polyfills take 900+KB.
image

@KishoreBarik
Copy link
Author

RxJs when polyfills are addded back.

image

@alan-agius4
Copy link
Collaborator

Hi @KishoreBarik, does the issue persist when updating to the latest versions of Angular CLI (8.2.x)?

Also, can you kindly provide a reproduction that we can look at? 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.

@alan-agius4 alan-agius4 added the needs: repro steps We cannot reproduce the issue with the information given label Aug 7, 2019
@KishoreBarik
Copy link
Author

Hi @alan-agius4
I tried updating Angular CLI to 8.2.x, but build was failing and found out following the error that angular core also needs to be updated to 8.x. Our team is not in a position to upgrade the project to 8.x. So I tried to create a repo to reproduce the error.

Reproduce steps are little different now. Pollyfills has been via angular.json (The actual project was upgraded from older angular, so polyfills were being added in main.ts). Please follow the Readme of the repo for reproduce steps.
Feel free to commit fixes.
Thanks.

@alan-agius4 alan-agius4 added area: @angular-devkit/build-angular needs: investigation Requires some digging to determine if action is needed and removed needs: repro steps We cannot reproduce the issue with the information given labels Dec 31, 2019
@ngbot ngbot bot modified the milestone: needsTriage Dec 31, 2019
@ngbot ngbot bot modified the milestones: needsTriage, Backlog May 27, 2020
@alan-agius4
Copy link
Collaborator

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.

If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: @angular-devkit/build-angular devkit/build-angular:browser freq1: low Only reported by a handful of users who observe it rarely needs: investigation Requires some digging to determine if action is needed severity1: confusing type: bug/fix
Projects
None yet
Development

No branches or pull requests

3 participants