Skip to content

Switch to npm #112

@chriswilty

Description

@chriswilty

Some things are just inherently tricky with modern Yarn, including the way Yarn versions are activated and managed, and also running a dependency audit, which needs a package-lock file to be generated first by npm.

I would like to suggest a switch to npm, which has caught up considerably with yarn in terms of features and ease-of-use.

Alternatively, we should consider switching to a modern Yarn version, as we are currently using Yarn Classic.

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesPull requests that update a dependency file

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions