Add support for reading environment variables from a `.env` file

Open
#92 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
typescript
Domain
cli

Research direction

Start by locating the configuration loading and command-line argument parsing entry points. Determine whether the .env file is read beside the config file or from the current directory, how values interact with the existing environment, and whether alternate filenames are in scope; done means the chosen behavior is validated and covered by tests.

Written by the indexing model from the issue text.

Description

S2

Several called tools use environment variables, but we're currently forcing those to be saved in the actual environment, which can be inconvenient for some users, so we should add support for reading additional environment variables from a .env file stored either in the same directory as the config file (or in the current directory - needs validation).

We should also consider adding a command line flag to configure alternative file names.

Dominant language
TypeScript
Stars
2
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from joewalker/loop-the-loop

All issues in joewalker/loop-the-loop

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.