Skip to content

packageManager missing warning by corepack #4378

@clicktodev

Description

@clicktodev

Description

error when running yarn install:

! The local project doesn't define a 'packageManager' field. Corepack will now add one referencing yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e.
! For more details about this field, consult the documentation at https://nodejs.org/api/packages.html#packagemanager

What is the problem?

risk of dev env inconsistency

How can we address it?

add packageManager field

Why is it important?

env consistency for a good dx

Who needs this?

doc maintainers

When should this happen (use version numbers if needed)?

asap

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