Closed alexeek closed 1 year ago
@NetanelBasal seems that you need to make a release for the last fix. I faced the same before. It looks like each release is cached and to be able to load the latest changes we need to release it after pr
or group of pr
s are merged.
@NetanelBasal ping you once more since there is a new similar issue.
Done
Which @ngneat/effects-* package(s) are the source of the bug?
effects-ng
Is this a regression?
Yes
Description
I wanted to update effects-ng from v2.0.0 to the latest. But
npm install
showsCould not resolve dependency
error. I found a similar error but looks like it's not fixed #45.Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw