Skip to content

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

Open
@IanButterworth

Description

@IanButterworth

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions