[legacy-framework] Load env variables based on APP_ENV or -e flag

[beerose]

Closes: blitz-js/legacy-framework#226

What are the changes and their implications?

Bug Checklist

• Integration test added (see test docs if needed)

Feature Checklist

• Integration test added (see test docs if needed)
• Documentation added/updated (submit PR to blitzjs.com repo canary branch): Add docs for setting custom app env name blitzjs.com#617

[beerose]

@flybayer I added the ability to set app env to dev, start, build, export. As for the other commands:

• new doesn't load anything from .env (or did I miss something)?
• db is deprectaed
• prisma — loads env variables inside of the prisma library, so that would need more changes right?
• generate, codegen, install, routes — doesn't need it?
• console — from what I see it doesn't load env variables, is that right?

---

I'll start working on the docs once we have the implementation.

[flybayer]

Ok this is looking good, but need a few more changes.

1. Set APP_ENV if -e present in next cli entrypoint.
2. Replace every call to dotenv-flow with a call to the next-env package
3. Remove dotenv-flow dependency

Prisma loads .env but none of the other files. So we previously called dotenv-flow which loaded the other files. Now we are replacing that with next-env.

[beerose]

update to latest

[beerose]

• Add integration tests
• Test locally the next package
• Brandon has to do a release with new @blitzjs/env package
• loadEnvConfig should default to process.cwd()