Skip to content

[feat] Consider adopting varlock #492

@theoephraim

Description

@theoephraim

You might want to consider adopting https://varlock.dev to manage config/.env files.

I believe you already understand the overall idea, as @ladjs/env seems to have some similar goals.

However varlock lets you combine your schema and defaults into a single source of truth, compose values together in more flexible ways, add additional validation logic, etc. It also helps protect any items marked as sensitive with log redaction and leak prevention. There is also a plugin system that helps pull values from various backends, like 1Password, with more on the way.

I'm happy to help implement and open a PR if there is interest.

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