Closed ryancwalsh closed 2 years ago
I added nvm use 17;
to the build command at https://dashboard.render.com/web/srv-c821j246fj315u4tlj90/settings
But then the next deployment said May 3 03:43:43 PM bash: nvm: command not found
.
Ahhh, I just found https://render.com/docs/node-version
That doesn't explain why this suddenly started being a problem, though, or why it's suddenly ignoring our package.json
.
I'll go ahead and try adding an env var anyway: NODE_VERSION=17.8.0
Funnily enough, the prior deployment succeeded even before I added that NODE_VERSION=17.8.0
, and then this deployment succeeded too.
I'll go ahead and close this issue even though I haven't diagnosed why there was a problem to begin with.
Looks like it failed after trying to rebuild after this commit fb3e8dc612f2782e69528b35953efae0288b5ea6, which is weird since that commit didn't even change anything that would've affected the web app side of things.
@encody Yeah I know; that's the first place I looked but I didn't see anything suspicious. It's bizarre.
At https://dashboard.render.com/web/srv-c821j246fj315u4tlj90/deploys/dep-c9omk6irrk01uqgjkcag I see:
I remember https://github.com/NEAR-Edu/near-certification-tools/issues/44
I don't know what is causing it to try to run 14.17.0.