Adjust build commands to use "next start"

codeforboston · Apr 2, 2024 · c430cb3 · c430cb3
1 parent 76da7ea
commit c430cb3
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/frontend/package.json b/frontend/package.json
@@ -4,10 +4,10 @@
   "private": true,
   "scripts": {
     "dev": "next dev",
-    "build:dev": "env-cmd -f .env.development next build && next export",
-    "build:stage": "env-cmd -f .env.staging next build && next export",
-    "build:prod": "env-cmd -f .env.production next build && next export",
-    "build:ui": "env-cmd -f .env.ui next build && next export",
+    "build:dev": "env-cmd -f .env.development next build && next start",
+    "build:stage": "env-cmd -f .env.staging next build && next start",
+    "build:prod": "env-cmd -f .env.production next build && next start",
+    "build:ui": "env-cmd -f .env.ui next build && next start",
     "lint": "next lint",
     "check-formatting": "prettier --check .",
     "prepare": "cd ${HOOKS_DIR:-..} && husky install frontend/.husky",