4.0.0

• [breaking change] Stricter strict mode! Now in strict mode, attempts to set a property on the cleaned env object, or an attempt to access a non-existing property on that object, will result in an error. See #44
• Also in strict mode, if you mistype an env var name, the error message will helpfully try and suggest the name that you meant to type (#50)
• New host and port validators (#55)
• Use prettier to enforce style conventions (#49)

Thanks in particular to @SimenB and @kachkaev for all their work and feedback that went into this release!

3.0.0

See the 3.0.0-beta release for a list of changes

3.0.0 beta

Backwards incompatible change

• In version 2.x, if you had a .env file that you were pulling env vars from, the env vars would also be added to process.env. As of envalid 3.x, those env vars are no longer copied to process.env, and are only available via the output of envalid.cleanEnv()

New features

• Added Typescript definitions (@ibratoev)
• Added new dotEnvPath option