ngneat / effects

🪄 A framework-agnostic RxJS effects implementation
https://www.netbasal.com
MIT License
63 stars 11 forks source link

Can't update effects-ng. Could not resolve dependency error #48

Closed alexeek closed 1 year ago

alexeek commented 1 year ago

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 shows Could 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

npm ERR! While resolving: app-workspace@2023.2.33
npm ERR! Found: @angular/router@15.2.2
npm ERR! node_modules/@angular/router
npm ERR!   @angular/router@"^15.1.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/router@"15.1.4" from @ngneat/effects-ng@3.1.0
npm ERR! node_modules/@ngneat/effects-ng
npm ERR!   @ngneat/effects-ng@"3.1.0" from the root project

### Please provide the environment you discovered this bug in

```true
"@angular/core": "^15.1.5",
    "@angular/forms": "^15.1.5",
    "@angular/platform-browser": "^15.1.5",
    "@angular/platform-browser-dynamic": "^15.1.5",
    "@angular/router": "^15.1.5",


### Anything else?

_No response_

### Do you want to create a pull request?

No
EricPoul commented 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 prs are merged.

EricPoul commented 1 year ago

@NetanelBasal ping you once more since there is a new similar issue.

NetanelBasal commented 1 year ago

Done