Skip to content

better handling of package.json in a workspace member #26146

Open
@nathanwhit

Description

@nathanwhit

Currently we only enable BYONM if the package.json is at the root. If the package.json is in a workspace member, we silently stop using BYONM and start using the global cache. This leads to confusing situations like #26125.

Metadata

Metadata

Assignees

No one assigned

    Labels

    clirelated to cli/ dirfeatnew feature (which has been agreed to/accepted)

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions