Skip to content

Migrate to modern Yarn #475

@Mikaela

Description

@Mikaela

#462 was (accidentally) trying to introduce this before falling back to #472 as the simpler option to get corepack enabled. I regardless thought that having a tracking issue wouldn't hurt so at least this won't get forgotten.

Draupnir is currently using Yarn 1.22.22 (also known as Classic) while the current release would be 4.3.1 (also known as Berry).

The Yarn website has three pages on benefits of the migration, the steps and optional steps.

In #462 the blocker was VS Code extension if I understood correctly and that would be possibly documented at:

Metadata

Metadata

Assignees

No one assigned

    Labels

    L1 Very FewLikelihoodP1 NuisancePriority levelT1 New FeatureUnrelated to any existing feature (must be used liberally)development specificIs an issue specific encountered by contributors when trying to develop DraupnirenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions