Skip to content

Peer Dependency error when using OSD v5.0.1 #215

@rssaini01

Description

@rssaini01

Hi,

Now, I am getting an issue with OpenSeadragon v5.0.1. I might be off here, but it looks like updating the peerDependency in the package.json could potentially resolve the issue. I did run npm install --legacy-peer-deps, and while the annotations appear to work with the newer version, I have a feeling this isn't a sustainable or proper long-term solution. Just wanted to check if updating the peer dependency directly would be a better approach. Thanks!

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error                                                                                                                                                                                                                           
npm error While resolving: @recogito/[email protected]
npm error Found: [email protected]
npm error node_modules/openseadragon
npm error   openseadragon@"^5.0.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer openseadragon@"^3.0.0 || ^4.0.0" from @recogito/[email protected]
npm error node_modules/@recogito/annotorious-openseadragon
npm error   @recogito/annotorious-openseadragon@"^2.7.18" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/openseadragon
npm error   peer openseadragon@"^3.0.0 || ^4.0.0" from @recogito/[email protected]
npm error   node_modules/@recogito/annotorious-openseadragon
npm error     @recogito/annotorious-openseadragon@"^2.7.18" from the root project
npm error
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.
npm error                                                                                                                                                                                                                           
npm error
npm error For a full report see:

Originally posted by @rssaini01 in #208 (comment)

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