Update supported node versions #1553
Assignees
Comments
|
Relatedly, I noticed that Auspice's Bioconda recipe is out of sync on Nodejs version compatibility. Opened a PR to fix it: bioconda/bioconda-recipes#37229 |
4 tasks
victorlin
added a commit
to nextstrain/auspice.us
that referenced
this issue
Oct 21, 2022
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
2 tasks
victorlin
added a commit
to nextstrain/auspice.us
that referenced
this issue
Oct 21, 2022
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
github-project-automation
bot
moved this from Prioritized
to Done
in Nextstrain planning (archived)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently our supported versions are "^12 || ^14 || ^16"
v12 has reached end-of-life and should be dropped
We should support v18. I'm running it day-to-day without problems, apart from needing the
NODE_OPTIONS=--openssl-legacy-providerflag. My understanding is that this should go away with webpack 5, introduced in #1520.The text was updated successfully, but these errors were encountered: