Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug(scope): Upgrade to v5 asks for @ngneat/transloco-utils #674

Closed
1 task done
bjornharvold opened this issue Jul 31, 2023 · 1 comment
Closed
1 task done

Bug(scope): Upgrade to v5 asks for @ngneat/transloco-utils #674

bjornharvold opened this issue Jul 31, 2023 · 1 comment

Comments

@bjornharvold
Copy link
Contributor

bjornharvold commented Jul 31, 2023

Is there an existing issue for this?

  • I have searched the existing issues

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.

Screenshot 2023-07-31 at 09 07 29 Screenshot 2023-07-31 at 09 07 05

This happens when I try to replicate in sandbox:
Screenshot 2023-07-31 at 09 13 33

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

Transloco: 5.0.0
Angular: 16.1.7
Node: 18.16.x
Package Manager: Yarn
OS: Mac

Browser

No response

Additional context

No response

I would like to make a pull request for this bug

Yes

#675

@shaharkazaz
Copy link
Collaborator

Thanks, Released in v 5.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants