[Richard]

Hi

Not sure exactly when this started happening but I have just noticed that each time I recompile an unchanged app the bundle size increases. For a simple one – 28.4Kb then 30.1 then 33.6 then 44.1. It grows exponentially until it crashes the server.

Fairly certain I have the latest of yours – Node.js v9.4 and

Any ideas as to the cause?

Cheers

Richard

[support-swapna]

Richard,

Sorry that you are seeing this issue.

1. Can you please clarify if you are working with an Angular app?
For an Angular app, the bundle size could depend on the Angular CLI version and if it is a prod/dev build.
Similar issue with bundle size is discussed here : https://github.com/angular/angular-cli/issues/8457

2. Is this problem specific to one particular Angular app? Are you using any build tools to build your app? Please share with us more details about how exactly you are building the app to help us investigate further.

3. If possible, please share with us the Terminal+ output from two consecutive builds to help us verify which bundles size in the app increased.

Apologies for inconvenience caused.

–Swapna
Genuitec Support

[Richard]

Hi Swapna

Thanks for the prompt response.

It is Angular apps that I am working with. I am working on a four different ones and they all exhibit this behavior.

The CLI is version 1.6.5 and they are all dev builds.

Just building with the CLI in your excellent IDE.

Terminal output follows – all I do for each new build is comment or uncomment the same line.

Cheers

Richard

Node.js version: v9.4.0
NPM version: 5.6.0
/Users/richardhirstle/eclipse-workspace/Appointments/node_modules/angular-ide/bin/ng serve –port=4200 –live-reload=true –webclipse-launch-id=7619596371385960526
** NG Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
10% building modules 3/3 modules 0 activewebpack: wait until bundle finished:
webpack: wait until bundle finished:
Date: 2018-07-21T00:43:16.519Z • Hash: c08d886f83244cb56eba • Time: 3831ms
5 unchanged chunks

webpack: Compiled successfully.
webpack: Compiling…
Date: 2018-07-21T00:43:25.402Z • Hash: d11a8ef4522c1a2513db • Time: 692ms
4 unchanged chunks
chunk {main} main.bundle.js, main.bundle.js.map (main) 10.9 kB [initial] [rendered]

webpack: Compiled successfully.
webpack: Compiling…
Date: 2018-07-21T00:43:33.883Z • Hash: ff87b32e54fe23e686c3 • Time: 345ms
4 unchanged chunks
chunk {main} main.bundle.js, main.bundle.js.map (main) 12.5 kB [initial] [rendered]

webpack: Compiled successfully.
webpack: Compiling…
Date: 2018-07-21T00:43:39.285Z • Hash: 46e6b1528f992c01db0f • Time: 793ms
4 unchanged chunks
chunk {main} main.bundle.js, main.bundle.js.map (main) 16 kB [initial] [rendered]

webpack: Compiled successfully.
webpack: Compiling…
Date: 2018-07-21T00:43:50.555Z • Hash: 958cb448a88bec9e9700 • Time: 268ms
4 unchanged chunks
chunk {main} main.bundle.js, main.bundle.js.map (main) 23.6 kB [initial] [rendered]

webpack: Compiled successfully.
webpack: Compiling…
Date: 2018-07-21T00:43:54.975Z • Hash: 3905820d872f08389caa • Time: 308ms
4 unchanged chunks
chunk {main} main.bundle.js, main.bundle.js.map (main) 40.7 kB [initial] [rendered]

webpack: Compiled successfully.

[support-swapna]

Richard,

Thank you for the details. I could replicate the problem at my end.
It looks like there is a known issue with multiple rebuilds which results in out of memory error.
A restart of the CLI server will reset the memory.

Please see these links :
https://github.com/angular/angular-cli/issues/5618
https://github.com/angular/angular-cli/issues/1652

I have escalated this issue to the dev team and they are looking into it to see if we can fix it at our end.
We will keep you posted about our findings.

Apologies for inconvenience caused.

–Swapna
Genuitec Support

[Author]

Posts