snowplow / snowplow/snowplow-javascript-tracker
Feature Request: Add support for custom environment file names
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 590
- Forks
- 232
- Avg merge
- 2h 22m
- Merged PRs (30d)
- 3
Description
Description
We are using the Snowplow JavaScript Tracker and the Snowtype CLI. According to the documentation, the CLI looks for a .env file to read credentials.
In our project, we use a file named .env.local for our environment variables. This requires us to either use dotenvx, or manually rename the file, or manage a separate .env file for the CLI to work, which can be cumbersome.
It would be a great quality-of-life improvement if the Snowtype CLI could accept a flag (e.g., --env-file or -e) to specify the path to a custom environment file. This would allow users to integrate the CLI more seamlessly into projects that use different naming conventions for environment files.
This change would enhance the flexibility of the tool and reduce friction for developers using a variety of project setups.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Snowtype CLI entry point and trace how it discovers the .env file. Add support for an --env-file or -e path, then verify that credentials are read from the specified file while the existing default behavior remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100