Support immer ^4.x.x

[JustFly1984]

I see errors while updating my project since I've updated immer to 4.0.0
although everything works without issues

Thank you for your work!

[mweststrate]

Please be a bit more descriptive Op zo 15 sep. 2019 22:43 schreef Alexey Lyakhov <notifications@github.com>:

…

I see errors while updating my project since I've updated immer to 4.0.0 although everything works without issues Thank you for your work! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#33?email_source=notifications&email_token=AAN4NBHO6PU227QQNKR6UMTQJ2UALA5CNFSM4IW4CEQ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HLOUMRQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAN4NBCOMVHF36WKPNLRPTTQJ2UALANCNFSM4IW4CEQQ> .

[JustFly1984]

please update your peer dependencies to "immer": "^4.0.0"

[danielkcz]

@JustFly1984 Peer dependency is about warning only during Yarn/NPM install. It's up to you update that in your project. If you are annoyed by warning, then submit a PR 😆

[JustFly1984]

10:07:02 PM: warning " > use-immer@0.3.3" has incorrect peer dependency "immer@^2.0.0 || ^3.0.0".

[danielkcz]

Sorry, but it's fairly silly. You open this issue like some catastrophic errors are happening... 😆

We have so many peer deps warnings in projects that we stopped worrying about those. Most of them are false positive of a wrong system. So it makes me smile every time when someone is concerned by the extra warning 😄

[nappy]

If the author would not be willing to maintain that range, or would be fine with just ignoring the error, why did not he just put an * in the first place? The only thing that is fairly silly here is your arguing. This is a completely legitimate issue.

[mweststrate]

This is indeed a valid issue, thanks for the PR @nappy !

[mweststrate]

Should be released as 0.3.3 now