Skip to content

Resolver error if a manifest contains a version that isn't in registries or local packages #4185

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

Open
IanButterworth opened this issue Mar 4, 2025 · 0 comments · May be fixed by #4186
Open

Comments

@IanButterworth
Copy link
Member

If a Manifest contains a newer version that the current session doesn't know about, say because the manifest is checked in and the local registry hasn't been updated recently, you can end up with resolver errors during a dev on the local package.

It'd probably be good to try updating registries beforehand, either every time dev is called, or just try again before throwing a resolver error.

@IanButterworth IanButterworth linked a pull request Mar 7, 2025 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant