Change semver range to not break on every new Angular release
bagbag opened this issue · comments
Instead of using "@angular/cdk": "^14.1.1", you could use "@angular/cdk": ">=14", or even >=12, if 12 or whatever version supports everything this lib needs).
Yes, this might break with a new Angular version, but most likely it will just work fine and we can get rid of using --force on npm install.
I will second this. Currently this is breaking the npm install for apps using Angular 14 + Angular Material 14.
@preel let me know if the issue is resolved with the new version. I will soon release the upgrade for angular 15 and also do note that noting is breaking you are just getting a warning ;)
It also looks like the material peer dependency is also pinned to a specific version. This would prevent upgrades for CVE fixes and would require this package to be bumped very often.
"@angular/material": "14.1.3",I agree that these peer dependencies should probably be ranges as indicated by @IliaIdakiev .