Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / envkey/envkey-node issues and pull requests
#28 - Incompatible with arm64 Linux EC2 instances
Issue -
State: closed - Opened by tmrclark about 3 years ago
- 1 comment
#27 - Modify default Key
Issue -
State: closed - Opened by jdesherlia about 3 years ago
- 2 comments
#26 - Adopt `envkey` to `next.js`
Issue -
State: closed - Opened by vespaiach almost 4 years ago
- 1 comment
#25 - Probably fix envkey-node on arm silicon macs
Pull Request -
State: closed - Opened by andrewphillipo about 4 years ago
- 1 comment
#24 - Apple Mac Silicon Issue
Issue -
State: closed - Opened by andrewphillipo about 4 years ago
- 2 comments
#23 - CLI version
Issue -
State: closed - Opened by magne4000 over 4 years ago
- 2 comments
#22 - Allow absolute paths in opts.dotEnvFile
Pull Request -
State: closed - Opened by elsbree over 4 years ago
#21 - Unable to use absolute file paths with envkey/loader
Issue -
State: closed - Opened by elsbree over 4 years ago
- 2 comments
#20 - Seems to break with TypeScript when built
Issue -
State: closed - Opened by shamoons over 4 years ago
- 3 comments
#19 - Can we override variables in a .env.test file?
Issue -
State: closed - Opened by shamoons over 5 years ago
- 3 comments
#18 - Error deploying to now.sh lambda
Issue -
State: closed - Opened by shamoons over 5 years ago
- 11 comments
#17 - Certificate signed by unknown authority
Issue -
State: closed - Opened by kevintc over 5 years ago
- 5 comments
#16 - check if property exists on env instead of if value exists
Pull Request -
State: closed - Opened by RGreenberger almost 6 years ago
- 1 comment
#15 - error: ENVKEY invalid
Issue -
State: closed - Opened by mkulgeorge about 6 years ago
- 1 comment
#14 - errors after upgrading to 1.2.4
Issue -
State: closed - Opened by selfagency about 6 years ago
- 7 comments
#13 - module size is massive
Issue -
State: open - Opened by jpiepkow about 6 years ago
- 6 comments
#12 - determine which envs should overwrite values
Issue -
State: closed - Opened by PatrickJS over 6 years ago
Labels: enhancement
#11 - determine when a Env is being used for a Key
Issue -
State: closed - Opened by PatrickJS over 6 years ago
Labels: enhancement
#10 - feat(applyVarsToEnv): include envs in envkey
Pull Request -
State: closed - Opened by PatrickJS over 6 years ago
#9 - boolean env values?
Issue -
State: closed - Opened by PatrickJS over 6 years ago
- 2 comments
#8 - Serverless-plugin-optimize breaking envkey
Issue -
State: closed - Opened by kvarela over 6 years ago
- 11 comments
#8 - Serverless-plugin-optimize breaking envkey
Issue -
State: closed - Opened by kvarela over 6 years ago
- 11 comments
#7 - Add additional logging when envkey cannot fetch
Issue -
State: closed - Opened by noqcks over 6 years ago
- 3 comments
#6 - async `envkeyLoader.load` doesn't callback with error on error
Issue -
State: closed - Opened by tony-g over 6 years ago
- 1 comment
#5 - Add Dev to tests for isDev
Pull Request -
State: closed - Opened by devotox over 6 years ago
#4 - Feature/Patch/Consideration: Custom dotEnvFile...
Issue -
State: closed - Opened by luncht1me over 6 years ago
- 2 comments
#3 - Cannot access environment variables while offline
Issue -
State: closed - Opened by selenium-tester almost 7 years ago
- 2 comments
#2 - 1.1.0 breaks
Issue -
State: closed - Opened by selfagency about 7 years ago
- 5 comments
#1 - ENVKEY invalid with freshly generated server key
Issue -
State: closed - Opened by collingo over 7 years ago
- 5 comments