From 62996773a454420630eab2a88874b7f9ad17bab8 Mon Sep 17 00:00:00 2001 From: dengqing Date: Wed, 18 May 2022 23:30:50 +0800 Subject: [PATCH] feat: support set NODE_ENV in scripts --- packages/vite/src/node/config.ts | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/packages/vite/src/node/config.ts b/packages/vite/src/node/config.ts index 02ce73c99a58c8..e9190f89d7bc56 100644 --- a/packages/vite/src/node/config.ts +++ b/packages/vite/src/node/config.ts @@ -395,7 +395,9 @@ export async function resolveConfig( // Note it is possible for user to have a custom mode, e.g. `staging` where // production-like behavior is expected. This is indicated by NODE_ENV=production // loaded from `.staging.env` and set by us as VITE_USER_NODE_ENV - const isProduction = (process.env.VITE_USER_NODE_ENV || mode) === 'production' + const isProduction = + (process.env.VITE_USER_NODE_ENV || process.env.NODE || mode) === + 'production' if (isProduction) { // in case default mode was not production and is overwritten process.env.NODE_ENV = 'production'