Skip to content

The dependency problem #887

@sagikazarmark

Description

@sagikazarmark

Viper has a huge number of dependencies.

This is the price paid for having a friendly API with all the features with zero configuration OOTB:

  • encoding/decoding from/into a large number of formats
  • reading from remote sources (etcd, firebase, etc)
  • having a filesystem abstraction library pulled in

In Viper 2, we should aim for lowering the number of dependencies. This is potentially a breaking change though.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions