Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[legacy-framework] fix blitz build not loading production env by default #3037

Merged
merged 1 commit into from
Dec 6, 2021
Merged

[legacy-framework] fix blitz build not loading production env by default #3037

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions packages/cli/src/index.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,11 @@ if (options.e || options.env) {
process.env.APP_ENV = options.e || options.env
}

// Have to copy this here from nextjs/packages/next/bin/next.ts before loadEnvConfig()
const defaultEnv =
process.argv[2] === "build" || process.argv[2] === "start" ? "production" : "development"
;(process.env as any).NODE_ENV = process.env.NODE_ENV || defaultEnv

// Load the .env environment variable so it's available for all commands
loadEnvConfig()

Expand Down