Motivation

Running vp build directly defaults NODE_ENV to "production", but running the same build through vp run build or vpr build received JavaScript null from the Vite Task environment client. Vite assigned that value to process.env.NODE_ENV, which Node coerced to "null", producing import.meta.env.DEV=true and PROD=false in production builds.

Fixes #2047.

Changes

• Pin Vite Task to the merged fix from fix(napi): return undefined for missing envs vite-task#508.
• Add a focused snapshot comparing direct vp build with vp run build.
• Verify an explicit NODE_ENV=test is preserved instead of being replaced with the production default.
• Cover a deploy task whose dependencies include build and db:migrate:prod, matching the follow-up report in vpr build sets NODE_ENV to "null" and produces development import.meta.env values #2047.
• Assert production builds expose NODE_ENV="production", DEV=false, and PROD=true.