Bug: conflicting version requirements of zone.js

Is this a bug, enhancement, or feature request?

This is a bug.

Briefly describe your proposal.

I tried to update my project to fundamental-ngx 0.23, it was already running on angular 10 (10.0.5 to be exact). So I updated my package json to 10.1.5 and ran into a conflicting specification of the required zone.js version.

Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.)

fundamental 0.23, angular 10.1.5

If this is a bug, please provide steps for reproducing it.

There are conflicting requirements for the zone.js library. If I configure package.json as "zone.js": "~0.11.2", I get the following error: @angular/core@10.1.5 requires a peer of zone.js@~0.10.3 but none is installed. You must install peer dependencies yourself.

If I configure "zone.js": "~0.10.3", then I get: @fundamental-ngx/core@0.23.0 requires a peer of zone.js@0.11.2 but none is installed. You must install peer dependencies yourself.

If I try to use a lower version of angular (e.g. 10.1.4), I get this error: @fundamental-ngx/core@0.23.0 requires a peer of @angular/core@~10.1.5 but none is installed. You must install peer dependencies yourself. Moving up to angular 10.1.6 doesn’t fix the problem and fundamental-ngx does not support any newer versions (angular 10.2.0) either.

In other words: fundamental-ngx/core makes conflicting demands: it specifies angular 10.1.5., which needs zone.js 0.10.3, but at the same time it specifies zone.js 0.11.2.

[JensSteckhan]

The problem is still there with fundamental 0.24.1:

@fundamental-ngx/core@0.24.1 requires a peer of zone.js@0.11.2 but @angular/core@10.2.3 requires a peer of zone.js@~0.10.3

[droshev]

@jenshuesken Can you try with npm v6?