Skip to content

Yarn outdated and upgrade-interactive should work in workspaces' packages also #4469

@marcofugaro

Description

@marcofugaro

Hey, I tried implementing Workspaces on a repo and here is some feedback that you might be interested in.

Basically I am having trouble running yarn outdated, yarn upgrade-interactive or other similar commands in a workspaces project.

What is the current behavior?
yarn outdated or yarn upgrade-interactive run from the root folder work only for the root package.json.
If I run those commands in a packages/* folder the error No lockfile in this directory. Run 'yarn install' to generate one. comes up.

What is the expected behavior?
yarn outdated or yarn upgrade-interactive should also check workspaces folders when run from root folder.

Please mention your node.js, yarn and operating system version.
yarn v1.0.2 with workspaces flag enabled
node v8.5.0

This is related to #4442

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