Skip to content
This repository was archived by the owner on Feb 17, 2025. It is now read-only.
This repository was archived by the owner on Feb 17, 2025. It is now read-only.

Consider switching from npm to yarn #10

@pyrello

Description

@pyrello

Motivation

I have mostly been using yarn as my node package manager on recent projects. When I originally pulled this down, I ran yarn install without even thinking about it. After realizing this was set up with npm, I ran npm install instead. Npm is much slower for me than yarn.

Proposed solution

  • Run yarn install to generate yarn.lock and add that file.
  • Remove 'package-lock.json` from the project.

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