Added fix to ssl issue based in webpack workaround

samilabud · Mar 4, 2024 · 2dc92b0 · 2dc92b0
1 parent aa2583e
commit 2dc92b0
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/client/package.json b/client/package.json
@@ -40,8 +40,8 @@
     "workbox-streams": "^5.1.3"
   },
   "scripts": {
-    "start": "react-scripts start",
-    "build": "react-scripts build",
+    "start": "react-scripts --openssl-legacy-provider start",
+    "build": "react-scripts --openssl-legacy-provider build",
     "test": "react-scripts test",
     "eject": "react-scripts eject"
   },

diff --git a/package.json b/package.json
@@ -2,6 +2,8 @@
   "name": "sam-server",
   "version": "1.0.0",
   "scripts": {
+    "client": "cd client && npm run start",
+    "server": "nodemon server.js",
     "dev": "concurrently --kill-others-on-fail \"npm run server\" \"npm run client\"",
     "start": "node server.js"
   },

diff --git a/server.js b/server.js
@@ -3,8 +3,6 @@ const path = require("path");
 const compression = require("compression");
 const enforce = require("express-sslify");
 
-//usar el .env si no estamos en produccion, de lo contrario setear las variables en produccion tipo:
-//heroku config:set STRYPE_SECRET_KEY=1234
 if (process.env.NODE_ENV !== "production") {
   require("dotenv").config();
 }