Skip to content

support package.json dependency changes #16

Description

@thymikee

When a dependency changes, e.g. when upgrading, it may cause a bug somewhere downstream in the app. Would be nice to have an option to detect where this dependency is used and include this information in the overall reverse-dependency tree. I expect it would often prompt almost all the tests to be re-run, so would prefer it to be optional, but worth experimenting.

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