5.2.0 ===== Export directly resolved values of string variables: * `nodeEnv` (for NODE_ENV) * `logLevel` (for LOG_LEVEL) Improve boolean environment variable resolution: * Handling of 'f' & 't' values * e.g. for `IS_LOCAL=t`, `isLocal` resolves to true * Fixed edge cases where detection was not case-insensitive `env` namespace consistently contains resolved values * Previously, some properties held the raw values Fix edge cases for string matching Major revamp of README Upgrade mad-logs & prettier 5.1.0 ===== Remove package lock (package-lock.json) Fix typings in outputted values (no more 'any' values) Add IDE-friendly docs to all exports Add handling for SKIP_BASIC_AUTH environment variable, with exports: * skipBasicAuth * isSkipBasicAuth * doSkipBasicAuth 5.0.1 ===== Switch transpile target to ES5 Remove mad-logs dependency (make devDependency instead) 4.1.0 ===== Add isLocal helper, for handling IS_LOCAL environment variable 4.0.1 ===== README brought up to date 4.0.0 ===== Remove most releaseEnvShort aliases: - releaseEnvAbbreviation - releaseEnvironmentShort - releaseEnvironmentAbbrev - releaseEnvironmentAbbreviation Remove all combined Mocha + LOG_LEVEL environment variable status aliases: - isVerboseMocha, isVerboseTest, isMochaVerbose, isTestVerbose - isVTest, isVMocha, isMochaV, isTestV - isDebugMocha, isDebugTest, isMochaDebug, isTestDebug - isSillyMocha, isSillyTest, isMochaSilly, isTestSilly Remove all isMocha (i.e. "Was this code run by Mocha?") aliases except isMochaEnv & runByMocha: - runViaMocha - runThruMocha - wasRunByMocha - wasRunViaMocha - wasRunThruMocha - loadedMochaOpts Remove isAvoidWeb alias: "doAvoidWeb" Remove isIECompat aliases: - isIECompatMode - isIeCompatMode Remove isReleaseEnvUAT aliases: - isUat - isReleaseEnvUat Remove isReleaseEnvQA aliases: - isQa - isReleaseEnvQa Remove LOG_LEVEL env var helper aliases: - isLogSilly - isLogVerbose - isLogDebug - isLogInfo - isLogWarn - isLogError - isLogWTF - isLogWtf - logGtEqlSilly - logGtEqlVerbose - logGtEqlDebug - logGtEqlInfo - logGtEqlWarn - logGtEqlError - logGtEqlWTF - logGtEqlWtf Overhaul & massively expand test suite Reformatted code, added more in-code docs 3.4.1 ===== Converted arrow functions to regular functions to satisfy Webpack + UglifyJS edge case 3.4.0 ===== Revamped so process.env.* vars are directly exposed (for webpack injection) 3.3.0 ===== Cleaner, shorter codebase: helpers generate exported env vars Module/Library/Engine upgrades: - Prettier -> v1.12 - Typescript -> v2.8.3 - Node -> v8.10.0 - ts-node: v5.0.0 -> v6.0.2 - mocha: v5.0.5 -> v5.1.1 - nodemon: v1.15.1 -> v1.17.3 - sinon: v4.4.9 -> v5.0.2 Simplified CHANGELOG format Build environment / utils: - Adds prettier config - Adds TSLint & TSLint config - Updates tsconfig.json to match new TS version - Adds TSLint rules plugins: - tslint-eslint-rules - tslint-microsoft-contrib - vrsource-tslint-rules - Adds typings for Mocha, Chai, & Sinon - Removed dependencies: - detect-node (removed altogether) - string.prototype.padend (removed altogether) - mad-logs (moved to devDependencies) New exported types: - LogLevel - NodeEnv - ReleaseEnvs type renamed to ReleaseEnvs New 'trace' LOG_LEVEL: - Adds trace log level (at lowest level) - Adds function isTrace (true if LOG_LEVEL=trace) Adds QA environment: - QA functions: isQA, isQa, isReleaseEnvQA, isReleaseEnvQa - Adds 'qa' as option to ReleaseEnv & ReleaseEnvShort types - Sets releaseEnvShort to 'qa' if detected RELEASE_ENV is QA (RELEASE_ENV=qa) New release environment detection functions (for existing release environments): - isReleaseEnvDev & isReleaseEnvDevelopment - isReleaseEnvProd & isReleaseEnvProduction Tests: - Adds LOG_LEVEL=verbose tests - Adds LOG_LEVEL=info tests - Adds LOG_LEVEL=error tests - Adds default LOG_LEVEL tests - Adds RELEASE_ENV=qa tests - Adds RELEASE_ENV=uat tests - Adds RELEASE_ENV=production tests 3.2.0 ===== Ran prettier on main file & other misc cleanups Proper export method for aliases (export {name as alias}) - Previous did extraneous duplicate object creations/var assignments & exported lodash types updated (to 4.14.104) Typescript -> 2.7.2 3.0.0 ===== Major overhaul Numerous subtle bugs were fixed, most/all of which were runtime and some of which could hypothetically reach production unnoticed. Some had the potential to result in e.g.: - parts of the application silently disappearing; - features being shut off - development logs becoming visible to end-users - the delivery of payloads that exclude browsers the application is required to support - due to task runners/transpilers overlooking environment variables that indicate that the build should include additional polyfills and/or extra transpilation steps for supporting less modern browsers). Thus, any usages that relied on broken exported values stop working as expected. Note that it's still fairly unlikely that many consumers of the library ran into this issue. Almost all of the issues related to the less convenient (albeit usually more accurate) aliases. Also, many (but not all) of these issues are fairly easy to detect if using Typescript. It's more likely that these features would simply not be used (they are rarely used in the internal production codebases for which this was developed), or would be detected in development. - I came across only one in our many codebases (which uses exports from this library 1000s of times) and discovered it before it reached production (this is what prompted the audit and repair of this library - the issue was very difficult to detect, and it caused an otherwise inexplicable show-stopping bug that took an extremely long time to trace to env-var-helpers). There's thus at least some potential for breakage since it's conceivable that someone may have run into our my issue but worked around it, so I felt a full major version upgrade was called for. Specific issues: 1) The older Mocha and test environment detecting exports relied on a manually set TEST_MODE environment variable. This was documented, but the documentation suggested this is the only thing the library uses for test detection. However, some of the exported properties use environment variable interally set by Mocha. The difference is now clearly identified. 2) If the "process" global variable is undefined, in certain environments the application will crash at runtime (by attempting to access properties of "undefined"). Our client builds inject process.env, and our commonly used environments are unaffected (side note: we inject process.env with a restricted subset of the backend properties. It is extremely dangerous and insecure to inject the entire contents of process.env into a client-side application) 3) If NODE_ENV is set to development or production, but the values are not in lowercase (e.g. NODE_ENV=PRODUCTION), both isDevelopment and isProduction would be outputted as false, causing sections of code to be unexpectedly skipped. Beyond these fixes, the test suite was overhauled and expanded to provide almost complete coverage (albeit only in a NodeJS environment - run through Mocha). There were numerous subtly broken tests, which have now been repaired. A set of convenience functions were also added to simulaneously detecting the log level and whether the current process was run by Mocha.