Skip to content

Drop weighty dependencies to keep subsequent libraries light #40

@kenotron

Description

@kenotron

Currently, the bulk of the dependencies come from the various lock file api's. They amount to nothing but two kinds of things:

  1. finding the right lock file with a find-up style convention
  2. parsing yaml
  3. stuffing the info obtained into a in-memory collection

I believe we can achieve these with much fewer dependencies so this library isn't so heavy

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