From 62be8e11e2397f65b773d377ee2bed5f8cf24f09 Mon Sep 17 00:00:00 2001
From: Chocobozzz <florian.bigard@gmail.com>
Date: Sat, 24 Jun 2017 10:17:44 +0200
Subject: [PATCH] Don't generate yarn lockfile on upgrade
---
package.json | 2 +-
scripts/upgrade.sh | 4 +---
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/package.json b/package.json
index ac542c3f9e..f795dff907 100644
--- a/package.json
+++ b/package.json
@@ -38,7 +38,7 @@
"update-host": "ts-node ./scripts/update-host.ts",
"test": "scripty",
"help": "scripty",
- "postinstall": "cd client && yarn install",
+ "postinstall": "cd client && yarn install --pure-lockfile",
"tsc": "tsc",
"nodemon": "nodemon",
"ts-node": "ts-node",
diff --git a/scripts/upgrade.sh b/scripts/upgrade.sh
index 748b0d947f..ff6dce94f4 100755
--- a/scripts/upgrade.sh
+++ b/scripts/upgrade.sh
@@ -25,9 +25,7 @@ fi
git pull origin $(git rev-parse --abbrev-ref HEAD) || exit -1
-yarn install
-yarn upgrade
-cd client && yarn upgrade && cd ../
+yarn install --pure-lockfile
npm run build
echo "\n\nUpgrade finished! You can restart PeerTube that may run the migration scripts."
--
GitLab