I understand that you don't want to support older builds of angular but please use more relaxed version targeting because now after every patch version of angular we receive warinings in npm:
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of [email protected] but none was installed.
(we have 2.4.5 and rx 5.0.3 installed)
To go along with what Boris is saying, you don't need to be up'ing a libraries Angular/Rx dependencies unless you're actually using those features (related to those fix branches).
So you could very well have it as ^2.0.0 which most libraries do, that avoids all of this. Just trying to help :)
"devDependencies": {
"@angular/core": "^2.0.0",
"@angular/common": "^2.0.0",
@MarkPieszak @hheexx definitely, sounds fair enough :)
Was just making sure, wasn't sure if you were using some of those features!
:)
I'll probably have to specify some angular package more strictly as there are some breaking features with the animations, but for rx or other it is then definitely the case.
In that case it may be better to specify that version after that breaking change for all packages. Like ^2.2.0 or ^2.3.0 - for all packages the same.
I'm not sure, maybe @MarkPieszak knows if there is any best practice about this?
Basically just the lowest common denominator 馃殌
Whatever lowest version works without breaking anything lol
This should be fine with your project now if you use version 0.8.0 :) Please reopen issue if still not OK :)
Thank you! 馃巿馃巿
Most helpful comment
@MarkPieszak @hheexx definitely, sounds fair enough :)