From f20313cddcf67d2bdfa6b8395a718a02229041ce Mon Sep 17 00:00:00 2001 From: Pavel Diatchenko Date: Fri, 7 Aug 2020 09:08:50 +1200 Subject: [PATCH] Remove node profiling from start script Is the --prof option (for profiling node) intentional? I blindly copied the script on my test server setup and ended up with a 17gb v8 log :smile: Anyone who runs `yarn start` or `npm start` is writing the profiling logs with this. I hope the one click Heroku deployment is using a different script --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 27a21a8eb..4dfa197d2 100644 --- a/package.json +++ b/package.json @@ -8,7 +8,7 @@ "ios": "browser.ios.js", "android": "browser.android.js", "scripts": { - "start": "node --prof examples/http.js", + "start": "node examples/http.js", "debug": "node --prof-process --preprocess -j isolate*.log > v8.json && rm isolate*.log && echo 'drag & drop ./v8.json into https://mapbox.github.io/flamebearer/'", "https": "HTTPS_KEY=test/https/server.key HTTPS_CERT=test/https/server.crt npm start", "prepublishOnly": "npm run unbuild",