Why are environment variables CaSE SEnsItiVE?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
Detecting and parsing environment variables should be case insensitive.
The reason is that Windows treats them so, and the people are pretty used to this behaviour.
I am used to set env vars in upper case so I expected export NODE_PRE_GYP_BUCKET=mybucket to work. I am happy to submit a PR for this.
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 by locating the environment-variable detection and parsing entry point, then inspect how NODE_PRE_GYP_BUCKET is read. Done means environment variable names are handled case-insensitively so the uppercase example works consistently with the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100