Specify Node version 16

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 ² nextstrain/auspice#1553
nextstrain · Oct 21, 2022 · 18390e4 · 18390e4
1 parent d6554a0
commit 18390e4
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/package-lock.json b/package-lock.json
diff --git 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",