fix: pnpm check messing up dev server

Author: LucHeart

package.json

@@ -5,8 +5,8 @@
 	"type": "module",
 	"scripts": {
 		"dev": "vite dev",
-		"build": "vite build",
-		"preview": "vite preview",
+		"build": "cross-env BUILD_ENV=production vite build",
+		"preview": "cross-env BUILD_ENV=production vite preview",
 		"prepare": "svelte-kit sync || echo '' && husky",
 		"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
 		"check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch",
@@ -38,6 +38,7 @@
 		"boxen": "^8.0.1",
 		"chalk": "^5.6.2",
 		"clsx": "^2.1.1",
+		"cross-env": "^10.1.0",
 		"eslint": "^10.2.1",
 		"eslint-config-prettier": "^10.1.8",
 		"eslint-plugin-compat": "^7.0.1",
@@ -82,4 +83,4 @@
 		"defaults and fully supports es6-module"
 	],
 	"packageManager": "pnpm@10.33.2"
-}
+}

pnpm-lock.yaml

@@ -9,7 +9,14 @@ import { loadEnv } from 'vite';
 const isGithubActions = process.env.GITHUB_ACTIONS === 'true';
 const isCloudflare = process.env.CF_PAGES === '1';
 const isDocker = process.env.DOCKER === 'true';
-const mode = process.env.NODE_ENV;
+// Don't trust NODE_ENV — tools like svelte-check load this file mid-process and
+// can have NODE_ENV='production' set by transitively-imported plugins (vite,
+// vite-plugin-svelte) even though no production build is actually happening.
+// `pnpm build`/`pnpm preview` set BUILD_ENV=production explicitly via cross-env;
+// CI/Cloudflare/Docker each have their own flag.
+const isProductionBuild =
+  isGithubActions || isCloudflare || isDocker || process.env.BUILD_ENV === 'production';
+const mode = isProductionBuild ? 'production' : 'development';
 
 const dotenv = { ...process.env, ...loadEnv(mode, process.cwd(), 'PUBLIC_') };