From 18390e4aabf04f76d501b32aca31e6df32ccd038 Mon Sep 17 00:00:00 2001
From: Victor Lin <13424970+victorlin@users.noreply.github.com>
Date: Fri, 21 Oct 2022 09:53:11 -0700
Subject: [PATCH] Specify Node version 16
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

It's recommended to set the Node version explicitly¹, otherwise the
build server chooses a default which can change unexpectedly. For
example, this change was prompted because Heroku recently switched from
16 to 18. Auspice doesn't work on 18 yet², so we need to use 16.

¹ https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
² https://github.com/nextstrain/auspice/issues/1553
---
 package-lock.json | 3 +++
 package.json      | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/package-lock.json b/package-lock.json
index bc22d8b..aed7803 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -12,6 +12,9 @@
       "dependencies": {
         "auspice": "2.39.0",
         "heroku-ssl-redirect": "0.0.4"
+      },
+      "engines": {
+        "node": "16.x"
       }
     },
     "node_modules/@ampproject/remapping": {
diff --git a/package.json b/package.json
index 03516b1..a76efe7 100644
--- a/package.json
+++ b/package.json
@@ -3,6 +3,9 @@
   "version": "0.12.0",
   "author": "James Hadfield",
   "license": "AGPL-3.0-only",
+  "engines": {
+    "node": "16.x"
+  },
   "scripts": {
     "modify-auspice-server": "node scripts/modify-auspice-server.js",
     "postinstall": "npm run modify-auspice-server",