Respect .nvmrc in addition to .node-version
complete
R
Robert Baird
I use nvm, Node Version Manager, to manage my Node.js version when developing. It'd be nice to have Render respect the version listed in the .nvmrc file that nvm uses to determine the node version when deploying instead of having to use a separate .node-version file.
Log In
Anurag Goel
complete
We now support reading the Node version from
.nvmrc
.Y
Yashu Mittal
Anurag Goel: The docs still have not been updated yet https://render.com/docs/node-version
C
Chris Castle
Yashu Mittal: Sorry about that! I've just updated the docs page you linked to. As an added bonus, we also support using version aliases. I've updated the docs to include this information too. See https://github.com/ehmicky/node-version-alias for more details about how we resolve version aliases to version numbers.
Anurag Goel
in progress
Anurag Goel
planned
M
Markus
Yes, this please!
Somewhat related: The docs say that Render respects the
engines
directive in package.json
, yet this does not work as expected with SemVer strings – in my case the value is { "node": "^14.0.0" }
, but Render is using Node 12.E
Emil Ahlbäck
Markus: Same problem here. "14.6" works fine, but not a semver string.
Anurag Goel
Emil Ahlbäck and Markus: we now support ranges in
package.json
as well as in the NODE_VERSION env var (which takes precedence).