use legacy openssl provider

mikeyavorsky · Jun 5, 2024 · b13e74f · b13e74f
1 parent 9962a66
commit b13e74f
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": "NODE_OPTIONS=--openssl-legacy-provider env-cmd -f .env.development next build && next export",
+    "build:stage": "NODE_OPTIONS=--openssl-legacy-provider env-cmd -f .env.staging next build && next export",
+    "build:prod": "NODE_OPTIONS=--openssl-legacy-provider env-cmd -f .env.production next build && next export",
+    "build:ui": "NODE_OPTIONS=--openssl-legacy-provider env-cmd -f .env.ui next build && next export",
     "lint": "next lint",
     "check-formatting": "prettier --check .",
     "prepare": "cd ${HOOKS_DIR:-..} && husky install frontend/.husky",