You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which Transloco package(s) are the source of the bug?
Transloco, Don't know / other
Is this a regression?
Yes
Current behavior
When I try to upgrade from 4.3.0 to 5.0.0 and run yarn, it asks me about which version of @ngneat/transloco-utils I want to use. When I manually add @ngneat/transloco-utils to package.json, yarn still asks me which version I would like to use.
This happens when I try to replicate in sandbox:
Comes up every time I run yarn:
warning Lockfile has incorrect entry for "@ngneat/transloco-utils@^4.0.0". Ignoring it.
Couldn't find any versions for "@ngneat/transloco-utils" that matches "^4.0.0"
? Please choose a version of "@ngneat/transloco-utils" from this list: (Use arrow keys)
❯ 5.0.0
Expected behavior
Running yarn should just download the new version of transloco.
Please provide a link to a minimal reproduction of the bug, if you won't provide a link the issue won't be handled.
Unable to download 5.0.0 into sandbox to replicate
Transloco Config
No response
Please provide the environment you discovered this bug in
Is there an existing issue for this?
Which Transloco package(s) are the source of the bug?
Transloco, Don't know / other
Is this a regression?
Yes
Current behavior
When I try to upgrade from 4.3.0 to 5.0.0 and run
yarn
, it asks me about which version of @ngneat/transloco-utils I want to use. When I manually add @ngneat/transloco-utils to package.json, yarn still asks me which version I would like to use.This happens when I try to replicate in sandbox:
Comes up every time I run yarn:
Expected behavior
Running yarn should just download the new version of transloco.
Please provide a link to a minimal reproduction of the bug, if you won't provide a link the issue won't be handled.
Unable to download 5.0.0 into sandbox to replicate
Transloco Config
No response
Please provide the environment you discovered this bug in
Browser
No response
Additional context
No response
I would like to make a pull request for this bug
Yes
#675
The text was updated successfully, but these errors were encountered: