Skip to content

Smarter handling for patch: dependencies #466

@dobesv

Description

@dobesv

When I have a dependency like:

    "i18next-phrase-in-context-editor-post-processor": "patch:[email protected]#./patches/i18next-phrase-in-context-editor-post-processor+1.3.0.patch",

I can't have multiple dependencies on that package in different workspaces as the path to the patch could be different. I suppose in this case the tool needs to resolve the path to the patch and verify that the absolute paths are equal instead of doing a simple string comparison.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions