Skip to content

Updating dependencies #621

@lrasmus

Description

@lrasmus

I am wondering if anyone else is getting the following error when running npm install:

npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

We have seen this for two separate developers now, and both can resolve it by using --legacy-peer-deps. However, I wanted to confirm that it wasn't something obvious or easily resolved that we had just missed.

Part of this is coming about as we have looked at updating dependencies in both the ui-client and api projects. We are still testing it, but our local version with updated dependencies (and some related changes) appears to do away with the above warning on the client side. Assuming this is an issue for others, and our changes continue to test well, we can submit a PR.

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