Open lomboboo opened 7 years ago
I believe that this gap is due to and/or expected for JIT Angular 2 applications. In JIT, a 1-2 second startup pause is expected. If you were using AoT you likely wouldn't see the same behavior, but this starter is JIT by default
@mcescalante Oh, I see. I actually found in Issues
that AoT will be added soon.
But for now, how can I integrate this behavior for production? Or it's not so simple to make it work with boilerplate?
So, I'm running Angular2 app with this awesome seed project (I really like it) and everything is awesome, except 1 thing:
when I moved it to production I noticed that initial load of app is over 2 secs. It is strange because app is really small, 5-6 simple api calls, some lightweight images, really small initial HTML size etc.
I started to investigate where is a problem, maybe some leaks in memory, but no. In Google chrome tools Network tab is showing some strange results:
What exactly is that gap over here? I'm new to Angular 2, maybe this is standard behavior? And if so, is it normal that such a small ng2 app loads so long?
Thanks, in advance