Skip to content

Question: package.lock and yarn.lock both exist #856

Open
@docrinehart

Description

@docrinehart

@ryanlanciaux Is the intent to support folks using either npm OR yarn? In my experience, we typically dictate one or the other for a project and that is the one you use for the project. I ran into some issues running npm install and I'm wondering if that's because I should have used yarn install.

Could you clarify for me if both are intended to exist or which package manager you'd prefer to keep around?

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