Skip to content

Package conflict in current version #222

Description

@biratkk

I just tried to clone the package locally, with the following conflict when trying to do npm install:
image

This was on Ubuntu 22.04.3 LTS. While doing npm i --force worked, I didn't expect to have this issue. If the issue is to be fixed later, I would suggest adding this disclaimer into the README.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions