Allow export VAR="value" syntax in dotenv files

[schickling]

It's a quite common use case to use the export keyword in .env files which enables you to run source .env without the need to additionally install any kind of tooling. Currently the now CLI doesn't pick up env vars prepended by an export statement.

Please support this case as well. 👍

[pranaygp]

Seems like the npm dotenv maintainers made the decision not to support export statements within .env files (motdotla/dotenv#118)

It also seems as if the suggested course of action is to use this auxiliary package (https://github.com/AndersDJohnson/dotenv-export) on a regular .env file (without the "export" statements)

[leo]

Sounds like a good idea if we can just support it without breaking the usual behaviour.

Though it seems like the package that was suggested (dotenv-export) is just a CLI for modifying existing dotenv files that don't yet have the keyword.

What we need is a package that supports parsing both the usual dotenv files and those with the export keyword inside.

[leo]

Thank you so much for the effort you have put into this issue! 😊

However, since we completely re-worked the entire codebase of Now CLI and this issue does not apply to the new code anymore, I'm closing it now.

You can read more about our biggest release yet here: https://zeit.co/blog/now-2