angular-seed-advanced icon indicating copy to clipboard operation
angular-seed-advanced copied to clipboard

The compilation time is degrading while editing files

Open VladimirMakaev opened this issue 7 years ago • 3 comments

I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior

If I run npm start or npm run start.deving and keep editing files. The compilation time keeps increasing after each time I save. Below is the terminal output of the time it takes build.js.dev to comlete. Finished 'build.js.dev' after 10 s Finished 'build.js.dev' after 21 s Finished 'build.js.dev' after 29 s Finished 'build.js.dev' after 39 s Finished 'build.js.dev' after 44 s Finished 'build.js.dev' after 54 s -- Restart Finished 'build.js.dev' after 9.66 s Finished 'build.js.dev' after 20 s Finished 'build.js.dev' after 27 s Finished 'build.js.dev' after 36 s Finished 'build.js.dev' after 42 s Finished 'build.js.dev' after 50 s In the end it doesn't matter even how many files I edit. A small change in a single file could result in > 1min compilation time.

Expected behavior

I expect the compilation times to be the same all the time as even compiling everything first time takes ~10secs

Minimal reproduction of the problem with instructions

  1. Run npm start
  2. Keep editing and saving files making the build to complete many times
  3. Notice the time increase for compilation over time

What is the motivation / use case for changing the behavior?

Development productivity is hugely affected.

Please tell us about your environment:

Mac OS Sierra (10.12.5 (16F73)), VS Code

  • Angular Seed Version: ea1e6e4da5
  • Node: node --version = v7.10.0

VladimirMakaev avatar Jun 10 '17 12:06 VladimirMakaev

This may offer some solutions to try: https://github.com/mgechev/angular-seed/issues/1905 Please post back which may help your condition.

NathanWalker avatar Jun 10 '17 17:06 NathanWalker

@NathanWalker I tried {isolatedModules: true} but the app doesn't start with that setting. I don't have any memory problems or crashes like in the issue you've mentioned. Just the duration of compilation keeps increasing

VladimirMakaev avatar Jun 12 '17 20:06 VladimirMakaev

Where exactly does one insert { isolatedModules: true } in this template?

joshcomley avatar Jul 14 '17 11:07 joshcomley