Bump angular dependencies

[vishal423]

Closes #9817

• Upgrade core-js

• Upgrade ng-jhipster

• Upgrade cache-loader

• Please make sure the below checklist is followed for Pull Requests.

• Travis tests are green

• Tests are added where necessary

• Documentation is added/updated where necessary

• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

[vishal423]

ng-jhipster updates are tracked under jhipster/ng-jhipster#95

[wmarques]

@vishal423 Maybe we can also change the lazy-loading module syntax to the new one using import()

[vishal423]

In v4.2, date objects are not being considered as valid (validations inbuilt into ng-bootstrap and introduced in v4.2). There is an open issue to track this: ng-bootstrap/ng-bootstrap#3215

Reverting to version before that works fine.

[vishal423]

@wmarques, I need to check on the lazy loading syntax change, specifically for JIT compilation as we use a separate library and I guess that doesn't yet support dynamic imports. I think this change can be made into separate PR.

[vishal423]

I spent some time to leverage new dynamic import syntax and observed few issues:

• Due to an issue in npm https://npm.community/t/packages-with-peerdependencies-are-incorrectly-hoisted/4794, AOT build fails. There is an associated open issue on webpack that provide more details: Parsing of import() fails in 4.29.0 (Compilation issue, related to dynamic import) webpack/webpack#8656 . It's also referenced in the angular CLI You may need an appropriate loader for dynamic imports after upgrade to Angular 8 angular/angular-cli#14566. I tried workaround suggested in the CLI ticket, but, that doesn't seem to work in my sample project. If you switch to yarn, then, AOT build works just fine.
• JIT build compiles with newer syntax, however, I don't see bundle splitting and all lazy loaded modules end up in the main bundle. I didn't debugged further due to AOT build issues.

[wmarques]

@vishal423 Ok then, let's merge this and we'll look onto that on a separate PR, thanks for your investigation 👍
Don't forget to claim your bug bounty ;)

[pascalgrimaud]

@vishal423 : can you explain me what is it plz ? Maybe we need to add this to Azure Pipelines too ?

[wmarques]

Angular CLI added an analytics feature (like us), this env variable prevents from sending data usage to the CLI project.
I don't think we need to add it into our pipeline as we don't rely on the angular CLI to build our application.

[vishal423]

In absence of this option, Travis builds got stuck in the post-install scripts (failed build logs @ https://travis-ci.org/jhipster/generator-jhipster/builds/539685496). I haven't noticed this issue on the Azure build pipleines (not sure why such discrepancy).

[DanielFran]

@wmarques Do not forget that it needs a new version of ng-jhipster.
See jhipster/ng-jhipster#95