Closed
Description
This issue impacts 9.0.0-rc.0 and happened while updating https://github.com/vmware/clarity.
Projects that contain tsickle in their dependencies will need the --force flag to be used during ng update:
kamik@RED-X1C6 MINGW64 /d/sandbox/clarity (update-9)
$ ng update @angular/cli @angular/core --next
The installed Angular CLI version is older than the latest published version.
Installing a temporary version to perform the update.
Installing packages for tooling via npm.
C:\Users\kamik\AppData\Local\Temp\.ng-temp-packages-s8KY7f\ng -> C:\Users\kamik\AppData\Local\Temp\.ng-temp-packages-s8KY7f\node_modules\@angular\cli\bin\ng
> @angular/cli@9.0.0-rc.0 postinstall C:\Users\kamik\AppData\Local\Temp\.ng-temp-packages-s8KY7f\node_modules\@angular\cli
> node ./bin/postinstall/script.js
+ @angular/cli@9.0.0-rc.0
added 254 packages from 205 contributors in 27.259s
Installed packages for tooling via npm.
Using package manager: 'npm'
Collecting installed dependencies...
Found 109 dependencies.
Fetching dependency metadata from registry...
Package "@angular-builders/dev-server" has an incompatible peer dependency to "@angular-devkit/build-angular" (requires ">=0.12.4", would install "0.900.0-rc.0")
. Package "tsickle" has an incompatible peer dependency to "typescript" (requires "~3.4.1", would install "3.6.4").
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.
This is a problem because tsickle used to be added to projects with libraries. We should be able to provide a tsickle version that supports TS 3.6.