From 2691d556fe9dbb6ef063642e84fc44631e7f4382 Mon Sep 17 00:00:00 2001
From: Richard Hansen <rhansen@rhansen.org>
Date: Mon, 15 Feb 2021 13:56:41 -0500
Subject: [PATCH] release: Enforce lockfileVersion 1

---
 src/bin/release.js | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/bin/release.js b/src/bin/release.js
index 6d08773d7..b0fb45ab2 100644
--- a/src/bin/release.js
+++ b/src/bin/release.js
@@ -62,6 +62,12 @@ writeJson('./src/package.json', pkg);
 childProcess.execSync('npm install --package-lock-only', {cwd: 'src/'});
 // run npm install --package-lock-only <-- required???
 
+// Many users will be using the latest LTS version of npm, and the latest LTS version of npm uses
+// lockfileVersion 1. Enforce v1 so that users don't see a (benign) compatibility warning.
+if (readJson('./src/package-lock.json').lockfileVersion !== 1) {
+  throw new Error('Please regenerate package-lock.json with npm v6.x.');
+}
+
 childProcess.execSync('git add src/package.json');
 childProcess.execSync('git add src/package-lock.json');
 childProcess.execSync('git commit -m "bump version"');