Open VladimirMakaev opened 7 years ago
This may offer some solutions to try: https://github.com/mgechev/angular-seed/issues/1905 Please post back which may help your condition.
@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
Where exactly does one insert { isolatedModules: true }
in this template?
I'm submitting a ... (check one with "x")
Current behavior
If I run
npm start
ornpm 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 takesbuild.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
npm start
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