-
-
Notifications
You must be signed in to change notification settings - Fork 187
Open
Labels
help wantedOpen to participation from the communityOpen to participation from the communityβ¨ goal: improvementImprovement to an existing featureImprovement to an existing featureπ status: ready for workReady for workReady for workπ aspect: docsConcerns the documentation in the repositoryConcerns the documentation in the repositoryπ© priority: lowLow priority and doesn't need to be rushedLow priority and doesn't need to be rushed
Description
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
- (comment) - npm - How can I specify the required Node.js version in package.json? - Stack Overflow
- JavaScript Guidelines β Creative Commons Open Source
Implementation
- I would be interested in implementing this feature.
Metadata
Metadata
Assignees
Labels
help wantedOpen to participation from the communityOpen to participation from the communityβ¨ goal: improvementImprovement to an existing featureImprovement to an existing featureπ status: ready for workReady for workReady for workπ aspect: docsConcerns the documentation in the repositoryConcerns the documentation in the repositoryπ© priority: lowLow priority and doesn't need to be rushedLow priority and doesn't need to be rushed
Type
Projects
Status
Backlog