Skip to content

Allow passing custom env instead of process.env #2549

Description

@ecraig12345

Mostly for testing purposes, it would be nice if ParseOptions included an env override, to be used instead of process.env. I know there are various mocking approaches that could work, but it would be simpler in my case to just pass through the desired value to parse().

If this sounds like a reasonable feature, I'd be happy to implement it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions