Problem
Currently there is not a consistent method across repositories for requiring a minimum Node.js version. This can and will create issues for contributing to repositories.
Description
This can be solved by adding guidance in the Javascript Guidelines to add:
"engines" : { "npm" : ">=x.y.z","node" : ">=x.yz"} to the package.json file as a baseline standard
Alternatives
Additionally, you can edit the .npmrc file to contain:
# .npmrc
engine-strict=true
but this provides inconsistent behavior, as local devs may have their own pre-existing .npmrc file.
A .nvmrc route is also possible and might have better outcomes
Additional context
Implementation
Problem
Currently there is not a consistent method across repositories for requiring a minimum Node.js version. This can and will create issues for contributing to repositories.
Description
This can be solved by adding guidance in the Javascript Guidelines to add:
"engines" : { "npm" : ">=x.y.z","node" : ">=x.yz"}to the package.json file as a baseline standardAlternatives
Additionally, you can edit the
.npmrcfile to contain:but this provides inconsistent behavior, as local devs may have their own pre-existing
.npmrcfile.A
.nvmrcroute is also possible and might have better outcomesAdditional context
Implementation