Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Environment variables get applied as options to any command #793
Is this a bug or feature request?
This is a bug.
What is the current behavior?
I have set
What is the expected or desired behavior?
Version information (for bug reports)
This make environment variable totally unusable... and it seems that web-ext use yargs to parse env variable (https://github.com/mozilla/web-ext/blob/master/src/program.js#L88). Should we move this to yargs or any other ideas to fix this?
Any updates here? I just killed over an hour trying to figure this out.
Hack I'm using to work-around this for now:
APIKEY="$WEB_EXT_API_KEY" APISECRET="$WEB_EXT_API_SECRET" unset WEB_EXT_API_KEY unset WEB_EXT_API_SECRET # Zip the Firefox extension. npx web-ext build --config-discovery=false # Zip+sign (XPI) the Firefox extension. npx web-ext sign \ --api-key=$APIKEY \ --api-secret=$APISECRET \ --config-discovery=false
OK, fair enough.
Perhaps adding something to the README and/or https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/web-ext_command_reference would suffice for now?