Return boolean values instead of "true"/"false" strings.

[becdot]

When boolean values are set in an .env file (e.g. IS_PRODUCTION=false), it's expected that these will be evalulated as booleans, instead of the string "false" (which is actually truthy). This causes particular problems when using webpack and webpack.DefinePlugin, since providing JSON.stringify(process.env.IS_PRODUCTION) will evaluate as truthy, which is unexpected.

Instead, change "true" to true and "false" to false when parsing the .env file.

[coveralls]

Coverage decreased (-2.3%) to 97.674% when pulling a226ac2 on becdot:becdot_eval_booleans into 46ec97d on motdotla:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 9a49866 on becdot:becdot_eval_booleans into 46ec97d on motdotla:master.

[coveralls]

Coverage remained the same at 100.0% when pulling d5442f9 on becdot:becdot_eval_booleans into 46ec97d on motdotla:master.

[coveralls]

Coverage remained the same at 100.0% when pulling d5442f9 on becdot:becdot_eval_booleans into 46ec97d on motdotla:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 27cfacf on becdot:becdot_eval_booleans into 46ec97d on motdotla:master.

[maxbeatty]

Thanks but we keep them as strings to align with how process.env behaves

Assigning a property on process.env will implicitly convert the value to a string.
– Node.js

envalid will do type conversion for you or you could write your own module focused on boolean behavior.

dotenv.config()
convertBooleans(process.env)

[becdot]

That makes sense -- thanks for the explanation!